Order 8260.19H Flight Procedures and Airspace
This document is cancelled. Cancelled by 8260.19I. Check the official source before relying on it.
Text read by OCR from a scanned file (85 of 476 pages). Check the original, as some words may be misread.
d. Chapter 2.
Distribution: Electronic Distribution Initiated By: AFS-400
CHANGE U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
ORDER 8260.19H CHG 1
National Policy
Effective Date:
04/26/2018
SUBJ: Flight Procedures and Airspace
1. Purpose. This change incorporates the updated Flight Standards organization structure while removing all Flight Standards routing symbols/codes. Also, this change transfers approval authority for special instrument flight procedures from the Flight Technologies and Procedures Division to the Flight Procedure Implementation and Oversight Branch. It assigns the Flight Procedure Implementation and Oversight Branch as the approval authority for instrument flight procedures that require specific approval (as identified in this and other 8260-series orders), or that require waivers to procedure design standards. In addition, the approval authority for Attention All Users Pages (AAUP) have been moved from the Flight Technologies and Procedures Division to the Flight Operations Branch. These changes are intended to reduce administrative redundancies and improve customer response times. Other editorial changes unrelated to policy and/or guidance have been made to correct publishing errors throughout the document.
2. Who this change affects. This change affects only the internal processes within Flight Technologies and Procedures Division.
3. Where You Can Find This Change. You can find this change on the Directives Management System (DMS) Website: http://www.faa.gov/regulations_policies/orders_notices.
4. Explanation of Changes. Significant areas of new direction, guidance, policy and/or criteria as follows:
a. General. Throughout the document, Flight Standards’ routing symbols/codes have been removed and replaced with the appropriate organizational title.
b. Chapter 1.
(1) Paragraph 1-2-2.a. Deleted last sentence that indicated the division (i.e., Flight Technologies and Procedures Division) is responsible for the approval/disapproval of special instrument flight procedures and waivers.
c. Paragraph 1-2-2.f. Revised description of Flight Procedure Implementation and Oversight Branch’s responsibilities to be inclusive of having the approval authority for specials, approvals, and waivers.
d. Chapter 2.
f. Chapter 8. › (11) Paragraph 8-10-4.
(1) Paragraph 2-12-1, General. Revised language to reflect the Flight Procedure Implementation and Oversight Branch may permit deviations to standards.
(2) Paragraph 2-12-6.a. Replaced “AFS-400” with “Flight Procedure Implementation and Oversight Branch.”
(3) Paragraph 2-12-6.c. Replaced “AFS-400” with “Flight Procedure Implementation and Oversight Branch.
e. Chapter 4.
(1) Paragraph 4-5-3.m. Replaced “AFS-400” with “Flight Procedure Implementation and Oversight Branch.”
f. Chapter 8.
(1) Table 8-3-2. In the top two rows related to Form 8260-1, replaced “AFS-400” with “Flight Procedure Implementation and Oversight Branch.”
(2) Paragraph 8-4-1. Replaced “AFS-400” with “Flight Procedure Implementation and Oversight Branch.”
(3) Paragraph 8-4-1.i. Revised text to remove “AFS-400” from the waiver process and to replace with “Flight Procedure Implementation and Oversight Branch.”
(4) Paragraph 8-5-2.t(4). Replaced “AFS-400” with “Flight Procedure Implementation and Oversight Branch.”
(5) Paragraph 8-6-9.j. Replaced “Flight Standards” with “Flight Procedure Implementation and Oversight Branch.”
(6) Paragraph 8-6-9.m. Replaced “Flight Standards” with “Flight Procedure Implementation and Oversight Branch.”
(7) Paragraph 8-6-10.o, Note 1. Replaced “AFS-400” with “Flight Procedure Implementation and Oversight Branch”
(8) Paragraph 8-6-11.o(2)(h). Replaced “AFS-400” with “Flight Procedure Implementation and Oversight Branch.”
(9) Paragraph 8-6-17. Replaced “AFS-400” with “Flight Procedure Implementation and Oversight Branch.”
(10) Paragraph 8-6-18.b(2). Replaced “AFS-460 Manager” with “Flight Procedure Implementation and Oversight Branch.”
(11) Paragraph 8-10-4. Revised to indicate Flight Operations Branch as the approval authority for AAUPs.
Dated
(12) Paragraph 8-10-5. Replaced instances of “AFS-400” with “Flight Operations Branch.”
(13) Paragraph 8-10-9.c. Replaced “AFS-400” with “Flight Operations Branch.”
PAGE CHANGE CONTROL CHART
Remove Pages Dated Insert Pages Dated
i through ii 07/20/2017 i through ii 04/26/2018 v through viii 07/20/2017 v through viii 04/26/2018 1-11 through 1-20 07/20/2017 1-11 through 1-20 04/26/2018 2-1 through 2-4 07/20/2017 2-1 through 2-4 04/26/2018 2-19 through 2-22 07/20/2017 2-19 through 2-22 04/26/2018 2-27 through 2-28 07/20/2017 2-27 through 2-28 04/26/2018 2-33 through 2-34 07/20/2017 2-33 through 2-34 04/26/2018 2-41 through 2-44 07/20/2017 2-41 through 2-44 04/26/2018 3-9 through 3-12 07/20/2017 3-9 through 3-12 04/26/2018 4-1 through 4-2 07/20/2017 4-1 through 4-2 04/26/2018 4-5 through 4-8 07/20/2017 4-5 through 4-8 04/26/2018 4-13 through 4-14 07/20/2017 4-13 through 4-14 04/26/2018 4-23 through 4-24 07/20/2017 4-23 through 4-24 04/26/2018 4-59 through 4-60 07/20/2017 4-59 through 4-60 04/26/2018 5-1 through 5-2 07/20/2017 5-1 through 5-2 04/26/2018 5-35 through 5-36 07/20/2017 5-35 through 5-36 04/26/2018 5-39 through 5-44 07/20/2017 5-39 through 5-44 04/26/2018 6-1 through 6-2 07/20/2017 6-1 through 6-2 04/26/2018 7-1 through 7-4 07/20/2017 7-1 through 7-4 04/26/2018 7-13 through 7-16 07/20/2017 7-13
through 7-16 04/26/2018 8-1 through 8-4 07/20/2017 8-1 through 8-4 04/26/2018 8-11 through 8-12 07/20/2017 8-11 through 8-12 04/26/2018 8-19 through 8-22 07/20/2017 8-19 through 8-22 04/26/2018 8-33 through 8-34 07/20/2017 8-33 through 8-34 04/26/2018 8-39 through 8-40 07/20/2017 8-39 through 8-40 04/26/2018 8-49 through 8-50 07/20/2017 8-49 through 8-50 04/26/2018 8-61 through 8-66 07/20/2017 8-61 through 8-66 04/26/2018 8-69 through 8-70 07/20/2017 8-69 through 8-70 04/26/2018 8-77 through 8-78 07/20/2017 8-77 through 8-78 04/26/2018 8-83 through 8-88 07/20/2017 8-83 through 8-88 04/26/2018 8-95 through 8-100 07/20/2017 8-95 through 8-100 04/26/2018 8-103 through 8-110 07/20/2017 8-103 through 8-110 04/26/2018 8-113 through 8-114 07/20/2017 8-113 through 8-114 04/26/2018 8-121 through 8-134 07/20/2017 8-121 through 8-134 04/26/2018 A-1 through A-4 07/20/2017 A-1 through A-4 04/26/2018 C-1 through C-2 07/20/2017 C-1 through C-2 04/26/2018
4. Distribution. This change is distributed electronically only.
John Duncan Executive Director, Flight Standards Service
SUBJ: Flight Procedures and Airspace
Distribution: Electronic Distribution Initiated By: AFS-400
Effective Date:
07/20/2017 National Policy
SUBJ: Flight Procedures and Airspace
This order provides guidance to all FAA personnel for the administration and accomplishment of the FAA Flight Procedures and Airspace Program.
The development of effective and efficient flight procedures is closely related to facility establishment and airport programs. These procedures require active participation by Flight Standards, the applicable Air Traffic Organization (ATO) Service Area, and office of Airports personnel in the planning, programming, and budgeting of navigation facilities and airport development plans. Instrument procedures often determine the alignment and location of navigation facilities as well as the location, marking, and lighting of airport landing and maneuvering areas. Title 14 Code of Federal Regulations (14 CFR) part 95 establishes minimum en route altitude (MEA), minimum reception altitude (MRA), maximum authorized altitude (MAA), minimum obstruction clearance altitude (MOCA), minimum crossing altitude (MCA), and changeover point (COP) are established by the Federal Aviation Administration for instrument flight along Federal airways.
General information and responsibilities are contained in chapter 1 and guidelines and procedures that are common to all instrument flight procedures are in chapter 2. Chapter 3 and 4 contain specific guidelines and procedures for en route and terminal instrument flight procedures, respectively. Chapter 5 contains information concerning airspace - obstruction evaluation (OE); designation of controlled airspace; airport airspace analysis; restricted areas; and establishment, relocation, or discontinuance of radio navigation aids. Chapter 6 provides information concerning Military procedures. Chapter 7 contains planning standards; airway, terminal, and airport planning; safety analysis; private aid, and facilities and equipment (F&E) support. Chapter 8 provides information on instrument approach procedures data transmittal systems as well as the use and preparation of forms.
ORDER 8260.19H
THIS PAGE IS INTENTIONALLY LEFT BLANK
Table of Contents
i
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-10
Section 1-2. Responsibilities … 1-11
1-2-1. Flight Standards Service … 1-11 1-2-2. Flight Technologies and Procedures Division … 1-11 1-2-3. Air Traffic Organization, Flight Program Operations … 1-14 1-2-4. Air Traffic Organization, Mission Support Services (AJV-0) … 1-15 1-2-5. Individual … 1-19
Chapter 2. General Procedures … 2-1
Section 2-1. General … 2-1
2-1-1. Requests for public-use IFPs … 2-1 2-1-2. Air Traffic Letters of Agreement (LOAs) … 2-1 2-1-3. Airport lighting and visual aids … 2-1
Section 2-2. Aeronautical Charts … 2-3
2-2-1. Use of maps and charts … 2-3 2-2-2. Aeronautical charts and publications … 2-3
Section 2-3. Environmental Requirements … 2-5
2-3-1. Noise abatement … 2-5 2-3-2. Environmental impacts … 2-5
Section 2-4. Facility Utilization and Monitoring … 2-6
2-4-1. Frequency Service Volumes … 2-6 2-4-2. ATC usable distance and altitude limitations … 2-6 2-4-3. Requests for Expanded Service Volumes … 2-8 2-4-4. Utilization of localizers … 2-9 2-4-5. Monitoring of navigation facilities … 2-9 2-4-6. Utilization of monitoring categories … 2-10 2-4-7. Utilization of 75 MHz markers … 2-10
Section 2-5. Implementing Epoch Year Magnetic Variation (MV) … 2-12
2-5-1. General … 2-12 2-5-2. Responsibilities … 2-12 2-5-3. Guidelines for Magnetic Variation (MV) revisions … 2-17
Table of Contents
ii
Section 2-6. Notices to Airmen (NOTAMs) … 2-20
2-6-1. General … 2-20 2-6-2. United States NOTAM System … 2-20
Section 2-7. Quality/Standardization of Instrument Flight Procedures … 2-21
2-7-1. Aeronautical Information Services action … 2-21 2-7-2. Flight Procedure Implementation and Oversight Branch’s action … 2-21
Section 2-8. Periodic Review of Instrument Flight Procedures … 2-22
2-8-1. General … 2-22 2-8-2. Reviewing organization action … 2-23
Section 2-9. Communications and Weather … 2-25
2-9-1. Communications requirements … 2-25 2-9-2. Use of UNICOM … 2-25 2-9-3. Automatic altimeter setting and weather reporting systems … 2-25
Section 2-10. Navigational Fixes … 2-26
2-10-1. General … 2-26 2-10-2. Reporting points … 2-26 2-10-3. Unplanned holding at designated reporting points … 2-26 2-10-4. Requests for navigational fixes … 2-26 2-10-5. Naming navigational fixes … 2-27 2-10-6. Documenting navigational fixes … 2-29 2-10-7. Correlation of navigational fixes and changeover points … 2-29 2-10-8. Minimum reception altitudes … 2-30 2-10-9. Flight inspection … 2-30 2-10-10. Maximum authorized altitudes … 2-31
Section 2-11. Obstacle Data … 2-32
2-11-1. General … 2-32 2-11-2. Obstacle application and data sources … 2-32 2-11-3. Obstacle data accuracy standards … 2-33 2-11-4. Accuracy standards application … 2-34 2-11-5. Controlling obstacles … 2-35 2-11-6. Datums … 2-40
Section 2-12. Waiver of Standards/Approval Requests … 2-42
2-12-1. General … 2-42 2-12-2. Waiver processing … 2-42 2-12-3. Waivers for Special Instrument Approach Procedures … 2-43 2-12-4. Safety Management System (SMS) requirements … 2-43 2-12-5. Periodic review of waivers … 2-44 2-12-6. Cancellation … 2-44
07/27/2017 Order 8260.19H Table of Contents
iii
Chapter 3. Route Procedures … 3-1
Section 3-1. General … 3-1
3-1-1. General … 3-1 3-1-2. Publication … 3-1
Section 3-2. Criteria Application and Development … 3-2
3-2-1. Criteria application … 3-2 3-2-2. Development of criteria … 3-2
Section 3-3. Establishment of En Route Airspace … 3-3
3-3-1. Relationship of COPs to airspace dimensions … 3-3 3-3-2. Relationship of MEAs to controlled airspace floors … 3-3
Section 3-4. Substitute En Route Flight Procedures … 3-4
3-4-1. General … 3-4 3-4-2. Format … 3-4 3-4-3. Facilities used … 3-4 3-4-4. Controlled airspace … 3-4 3-4-5. Flight Inspection … 3-4 3-4-6. Planning and coordination … 3-5 3-4-7. Processing … 3-8 3-4-8. Periodic review … 3-8 3-4-9. Distribution … 3-8
Section 3-5. Off-Airway Routes … 3-10
3-5-1. Establishment … 3-10 3-5-2. Listing … 3-10 3-5-3. Off-airway data … 3-10 3-5-4. Processing data to NFDC … 3-11
Section 3-6. New or Revised National Airspace System Routes … 3-12
3-6-1. Definition - Route … 3-12 3-6-2. Coordination Procedures … 3-12 3-6-3. Publication of procedural data … 3-12
Section 3-7. Minimum Vectoring Altitude (MVA) and Minimum IFR Altitude (MIA) Charts ... 3-13
3-7-1. Chart preparation … 3-13 3-7-2. Obstacle clearance … 3-13 3-7-3. Controlled airspace … 3-13 3-7-4. Chart review and approval … 3-13 3-7-5. Emergency Obstruction Video Map (EOVM) … 3-14
Chapter 4. Terminal Procedures … 4-1
Section 4-1. General … 4-1
4-1-1. General … 4-1 4-1-2. Categories of Instrument Approach Procedures … 4-1 4-1-3. Airspace requirements … 4-1 4-1-4. Contractual use of private facilities … 4-2
07/27/2017 Order 8260.19H Table of Contents
iv
4-1-5. TERPS application … 4-2 4-1-6. Sidestep maneuvers … 4-3 4-1-7. Temporary displaced threshold procedures … 4-4
Section 4-2. Standard Instrument Approach Procedures (SIAP) … 4-5
4-2-1. General … 4-5 4-2-2. Coordination of Terminal Instrument Procedures … 4-5 4-2-3. Radar Instrument Approach Procedures … 4-5
Section 4-3. Category II and III ILS … 4-6
4-3-1. General … 4-6 4-3-2. Action … 4-7 4-3-3. NOTAM requirements … 4-8
Section 4-4. Departure Procedures (DP) … 4-9
4-4-1. General … 4-9 4-4-2. Diverse Vector Area (DVA) … 4-9
Section 4-5. Standard Terminal Arrival (STAR) … 4-10
4-5-1. General … 4-10 4-5-2. Roles and responsibilities … 4-16 4-5-3. Preparation of Form 8260-17.1 … 4-20 4-5-4. Preparation of Form 8260-17.2 … 4-45
Section 4-6. RNAV Procedure Development … 4-55
4-6-1. General … 4-55 4-6-2. RNAV Approach Procedure design … 4-55 4-6-3. Developing RNAV waypoint … 4-57 4-6-4. RNAV leg types … 4-59 4-6-5. RNAV leg type descriptions … 4-59 4-6-6. Final Approach Segment (FAS) data … 4-60 4-6-7. Remote altimeter setting for Baro-VNAV … 4-60 4-6-8. Critical temperature … 4-60 4-6-9. DME/DME screening model … 4-60 4-6-10. Additional documentation with Baro-VNAV … 4-61
Chapter 5. Airspace … 5-1
Section 5-1. Obstruction Evaluation (OE) … 5-1
5-1-1. General … 5-1 5-1-2. Responsibility and Processing of Form 7460-1 … 5-1 5-1-3. Review of Notices … 5-1 5-1-4. Adjustments to Instrument Flight Procedures … 5-1
Section 5-2. Designation of Controlled Airspace … 5-2
5-2-1. General … 5-2 5-2-2. Air Traffic Responsibility … 5-2 5-2-3. Aeronautical Information Services action … 5-2 5-2-4. Terminal Airspace … 5-3
Table of Contents
v
Section 5-3. Airport Airspace Analysis … 5-39
5-3-1. General … 5-39 5-3-2. Service Area OSG-FPT/Flight Standards inputs … 5-39 5-3-3. Flight Standards performs the flight safety review of airport proposals … 5-39 5-3-4. Service Area OSG-FPT is responsible for evaluation … 5-39 5-3-5. Alterations of airports or heliports … 5-40 5-3-6. Deactivation of airports or heliports … 5-40 5-3-7. Assistance in zoning problems … 5-41
Section 5-4. Restricted Areas … 5-42
5-4-1. General … 5-42 5-4-2. Letter of procedures … 5-42
Section 5-5. Establishment, Relocation, or Discontinuance of Radio Navigation Aids … 5-43
5-5-1. Criteria and guidelines … 5-43 5-5-2. OSG-FPT action … 5-43 5-5-3. Flight Standards action … 5-43
Chapter 6. Military Procedures … 6-1
6-1-1. General … 6-1 6-1-2. Review and coordination … 6-1 6-1-3. FAA acceptance … 6-1 6-1-4. Assistance … 6-1
Chapter 7. Planning … 7-1
Section 7-1. General … 7-1
7-1-1. General … 7-1
Section 7-2. Planning Standards … 7-2
7-2-1. Planning standards … 7-2 7-2-2. Determination of operational benefits/improvements … 7-2
Section 7-3. Safety Analysis … 7-4
7-3-1. Performing a Safety Analysis … 7-4
Section 7-4. Airway Planning … 7-7
7-4-1. General … 7-7
Section 7-5. Terminal Planning … 7-8
7-5-1. General … 7-8 7-5-2. Requirements for outer compass locators … 7-8
Section 7-6. Airport Planning … 7-13
7-6-1. General … 7-13
Section 7-7. Private Aid … 7-14
7-7-1. General … 7-14
Section 7-8. Facilities and Equipment (F&E) Support … 7-15
7-8-1. Support … 7-15
Table of Contents
vi
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-4 8-2-5. Terminal routes - General … 8-5 8-2-6. Terminal fixes … 8-9
Section 8-3. Certification, Processing, and Review … 8-11
8-3-1. General … 8-11 8-3-2. Certification and processing of SIAPs … 8-11 8-3-3. Cancellation/Suspension of Instrument Approach Procedures … 8-11 8-3-4. Revisions to IFPs … 8-12 8-3-5. Aeronautical Information Services review of SIAPs and charts … 8-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, FAA Form 8260-1 … 8-21
8-4-1. Preparation of Form 8260-1 … 8-21
Section 8-5. Radio Fix and Holding Data Record, FAA Form 8260-2 … 8-24
8-5-1. Introduction … 8-24 8-5-2. Preparation of Form 8260-2 … 8-24
Section 8-6. Completion of FAA Forms 8260-3/4/5/7A … 8-35
8-6-1. General … 8-35 8-6-2. Basic information … 8-35 8-6-3. Terminal Arrival Area (TAA) … 8-38 8-6-4. Terminal routes … 8-40 8-6-5. Radar terminal area maneuvering sectors and altitudes … 8-43 8-6-6. Missed Approach … 8-43 8-6-7. Profile - Lines 1 through 8 … 8-48 8-6-8. Equipment requirements notes for conventional … 8-55 8-6-9. Notes … 8-57 8-6-10. Additional flight data … 8-65 8-6-11. Minimums … 8-70 8-6-12. Changes and reasons … 8-82 8-6-13. Coordinated with … 8-82 8-6-14. Submitted by … 8-83 8-6-15. Flight checked by Inspection/validation official … 8-83 8-6-16. Developed by … 8-84 8-6-17. Recommended by … 8-84
Table of Contents
vii
8-6-18. Approved by … 8-84 8-6-19. FAS Data Block Information … 8-84
Section 8-7. Standard Instrument Approach Procedure Data Record, FAA Form 8260-9 … 8-85
8-7-1. Preparation of Form 8260-9 … 8-85
Section 8-8. Transmittal of Airways/Route Data Record, FAA Form 8260-16 … 8-95
8-8-1. Preparation of Form 8260-16 … 8-95
Section 8-9. Simultaneous Close Parallel (SCP) and Simultaneous Offset Instrument
Approach (SOIA) Procedure Attention All Users Page (AAUP) … 8-121 8-9-1. Attention All Users Page … 8-121 8-9-2. Site Implementation Team … 8-121 8-9-3. AAUP preparation … 8-121 8-9-4. AAUP processing … 8-121 8-9-5. AAUP publication … 8-121 8-9-6. Forms processing … 8-122 8-9-7. Title line … 8-122 8-9-8. Text … 8-122 8-9-9. Administrative information … 8-125
Appendix A. Administrative Information … A-1
Appendix B. Flight Procedures References … B-1
Appendix C. Obstacle Accuracy Standards, Codes, and Sources … C-1
Appendix D. FAA Form 8260-2, Data Worksheet … D-1
Appendix E. Radio Fix and Holding Data Record Form … E-1
Appendix F. ILS and RNAV Standard Instrument Approach Procedure Form … F-1
Appendix G. Radar – Standard Instrument Approach Procedure Form … G-1
Appendix H. Standard Instrument Approach Procedure Form … H-1
Appendix I. Special Instrument Approach Procedure and Special Instrument Procedure Authorization … I-1
Appendix J. Standard Instrument Approach Procedure … J-1
Appendix K. FAS Data Block Requirements … K-1
Appendix L. FAS Data Block Requirements for Helicopter Operations … L-1
Appendix M. Instrument Flight Procedures (IFP) Lifecycle … M-1
Table of Contents
viii
THIS PAGE IS INTENTIONALLY LEFT BLANK
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.
a. General. › (5) Deleted requirement throughout this directive, including the former…
1-1-2. Audience. The primary audience for this order is the Air Traffic Organization (ATO) Mission Support Services (MSS) (hereafter referred to as “AJV”), all service providers (as defined in appendix A), and elements of the Armed Forces described in Title 10 of the United States Code (hereafter referred to as “military”) who have the responsibility to develop instrument flight procedures (IFPs). The secondary audience includes all other Air Traffic organizations, Flight Standards Service, and other organizations who have responsibilities related to IFP development.
Note: Users of this order can refer to appendix A for an alphabetical listing of frequently used acronyms and abbreviations.
1-1-3. Where you can find this order. You can find this order on the FAA’s web site.
1-1-4. What this order cancels. Order 8260.19G, Flight Procedures and Airspace, dated 07/14/2015, is canceled.
1-1-5. Explanation of changes. Significant areas of new direction, guidance, policy, and criteria as follows:
a. General.
(1) Changed all references from “AIS” to “Aeronautical Information Services.”
(2) Changed all references from “Flight Inspection Services” and “AJW-3” to “Flight Program Operations.”
(3) Changed all references from “Airport/Facility Directory (A/FD)” to “Chart Supplement.”
(4) Changed all references from Regional Flight Standards Division (RFSD) to All Weather Operations (AWO) to reflect changes being made regarding Flight Standards Realignment organizational changes.
(5) Deleted requirement throughout this directive, including the former appendix N, which addressed documentation of waypoint description codes on 8260-series forms. This now permits database developers to establish/code them when required.
d. Chapter 2. › (4) Paragraph 2-5-3.b and 2-5-3.c. Per the Performance-based Operations…
(6) Added “/validation” following “flight inspection” where a flight validation is appropriate for procedures developed by non-FAA service providers.
(7) Removed references to “OTA” that were previously missed and replaced with “non- FAA service provider.”
(8) Deleted section 1-3, Instrument Procedure Development Software Responsibilities. These responsibilities are specified in applicable 1100-series directives and organizational agreements that are subject to constant internal organizational changes.
(9) Per discussion at Aeronautical Charting Forum, Instrument Procedures Group (ACF- IPG) meeting 16-01, all Fahrenheit temperatures have been removed. All temperatures will be specified in Celsius only.
(10) Removed all items pertaining to documenting “All affected procedures reviewed” in an 8260-series form block; this block has been removed from the revised forms. Review requirements are specified in section 2-8, “Periodic Review of Instrument Flight Procedures.”
(11) Removed references to ARINC and ARINC 424 and replaced with appropriate text to refer to the database coding used by aircraft navigation systems.
(12) Changed all “turbojet” references to just “jet.”
b. Table of Contents. Updated to coincide with the pages changed.
c. Chapter 1.
(1) Added Regulatory reference to comply with Order FS 8000.96, Flight Standards Service Guidance Document Development, paragraph 3.7.
(2) Paragraph 1-2-4.c. Inserted new paragraph to address Air Traffic Standards & Procedures Directorate (AJV-8) responsibilities and up-lettered the following paragraphs.
d. Chapter 2.
(1) Paragraph 2-2-2. Updated office contacts.
(2) Paragraph 2-4-3.a. Clarified intent of the requirement by stating that there is a need for an expanded service volume for aircraft navigating outside both the lateral and vertical boundaries shown for each navigational aid (NAVAID) type.
(3) Paragraph 2-4-4. Editorial changes for clarity and added guidance to address Flight Program Operations’ concerns over proper use of localizers for missed approach procedures.
(4) Paragraph 2-5-3.b and 2-5-3.c. Per the Performance-based Operations Aviation Rulemaking Committee (PARC) recommendation to AVS-1 dated April 22, 2016, “VOR/VORTAC” magnetic variation tolerance changed from three degrees to five degrees.
(5) Section 2-6. Moved all Flight Data Center (FDC) Notices to Airmen (NOTAM) policy to Order JO 7930.2, Notices to Airmen. Retained select information that will point the reader to where instrument flight procedures FDC NOTAM guidance can be obtained.
d. Chapter 2. › (19) Paragraph 2-11-3.b(6) thru (9). Deleted. Moved guidance to…
(6) Paragraph 2-7-2.b. Deleted last sentence as it was considered redundant; previous paragraph cover the task.
(7) Paragraph 2-8-2(2)(e). Deleted “Verify continued need for IFPs and cancel IFPs that are no longer required” as procedure use is not tracked and there is no clear way to make this determination.
(8) Paragraph 2-8-2.b(3). Deleted paragraph.
(9) Paragraph 2-10-4.a(6). Added Note to resolve problems being experienced when processing fix/holding pattern changes that impact both public and Special instrument procedures.
(10) Paragraph 2-10-4.b. Deleted requirement to use waypoints for area navigation (RNAV) standard instrument approach procedures (SIAP) on Victor Airways; See ACF IPG agenda item 14-01-316.
(11) Paragraph 2-10-5.a(4)(d). Deleted paragraph.
(12) Paragraph 2-11-1. Established guidance to not require obstacle assessments to be conducted for operations above 18,000 feet in the contiguous U.S. or above 23,000 feet for Alaska and Hawaii.
(13) Paragraph 2-11-2.a. Editorial changes to responsibilities and added guidance to allow data to be accepted from additional methods/sources.
(14) Paragraph 2-11-3. Removed the word “code” following the word “accuracy” where used; i.e., where “accuracy code adjustment” was used, it will state “accuracy adjustment,” where appropriate. Intent is to prevent procedure developer from believing that the “code” value specified in the appendix C tables must be used in all cases when an assigned accuracy value may be provided and used where digital terrain elevation data (DTED) and digital elevation model (DEM) information is used.
(15) Paragraph 2-11-3.b(1). Changed 1A accuracy requirement for missed approach to only apply to section 1 of the missed approach.
(16) Paragraph 2-11-3.b(3). Added sloping surface for visual climb over airport (VCOA).
(17) Paragraph 2-11-3.b(4). Added reference to climb-in-holding.
(18) Paragraph 2-11-3.b(5). Added reference to “DPs” to be consistent with previous paragraph.
(19) Paragraph 2-11-3.b(6) thru (9). Deleted. Moved guidance to paragraph 2-11-4.
f. Chapter 4. › (4) Paragraph 4-5-1.b(10). Removed reference to “Bottom Altitude” as it…
(20) Paragraph 2-11-4. Editorial and added statement to not apply accuracy adjustment to departure procedure controlling obstacles defined for determining ceiling and/or visibility.
(21) Paragraph 2-11-4.a. Editorial change to refer to the “applicable FAA Form,” as opposed to just the Form 8260-9, Standard Instrument Approach Procedure Data Record.
(22) Paragraph 2-11-4.c. Added sentence to ensure accuracy value is applied when evaluating proposed obstruction information impact on instrument flight procedures.
(23) Paragraph 2-11-4.d. Editorial revision for clarity and added guidance to address accuracy adjustments when there are multiple controlling obstacles.
(24) Paragraphs 2-11-5.b(2)(a) Exception and 2-11-5.c(1)(b). Removed the word “lateral.”
(25) Paragraph 2-11-5.d. Inserted new paragraph to address controlling obstacle for VCOA procedures. Following paragraph up-lettered.
(26) Paragraph 2-12-6. Removed reference to “waiver” in beginning sentence and added paragraph to address the Flight Standards “approval” process when the approval is no longer applicable.
e. Chapter 3.
(1) Paragraph 3-5-2. Updated guidance to support off-airway routes developed by non- FAA service providers.
(2) Paragraph 3-5-3. Updated guidance to support off-airway routes developed by non- FAA service providers.
(3) Paragraph 3-5-4. Updated guidance to support off-airway routes developed by non- FAA service providers.
f. Chapter 4.
(1) Paragraph 4-1-6. Removed all terminal instrument procedures (TERPS)-related criteria for the sidestep maneuver that is now located in Order 8260.3, U.S. Standard for Terminal Instrument Procedures (TERPS), chapter 2. Retained only guidance pertaining to documenting and publishing sidestep information.
(2) Paragraph 4-5-1.b(5). Added note stating not to reference an altitude as one that can be expected to be assigned by air traffic control (ATC) due to proven misapplication and confusion this has caused that resulted in unintended consequences.
(3) Paragraph 4-5-1.b(8)(b). Added new paragraph to support request from ACF-IPG agenda item 15-01-293, STAR Terminus Point Standardization.
(4) Paragraph 4-5-1.b(10). Removed reference to “Bottom Altitude” as it will not be specifically annotated as such on the chart. Paragraph rewritten to refer to the altitude required at
the standard terminal arrival route (STAR) termination point, per Order 8260.3, paragraph 2-2-1.f(6).
h. Chapter 8. › (3) Paragraph 8-3-2.a(2). Editorial change.
(5) Paragraph 4-5-1.d(3)(f). Added that an airport name, airport identifier, and/or city/state change can be done by abbreviated amendment.
(6) Paragraph 4-5-3.j(5). Deleted paragraph pertaining to “Bottom Altitude.”
(7) Paragraph 4-5-3.n. Consolidated “changes” and “reasons.”
(8) Paragraph 4-5-4.i, table 4-5-2. Added indicator for block altitude.
(9) Paragraph 4-6-2.a(1). Removed the word “all” from the sentence.
(10) Paragraph 4-6-2.a(5). Removed “or any point prior to the PFAF” to be consistent with criteria established in Order 8260.3, section 2-2.
(11) Paragraph 4-6-2.e note. Added statement that the Terminal Arrival Area concept not be used on instrument landing system (ILS)/localizer (LOC) procedures containing a conventional missed approach.
(12) Paragraph 4-6-4.c. Deleted, no longer required.
(13) Paragraph 4-6-5.d. Removed course-to-altitude (CA) leg guidance that has been moved to Order 8260.58, U.S. Standard for Performance Based Navigation (PBN) Instrument Procedure Design.
(14) Paragraph 4-6-10.e. Paragraph revised to remove chart note: “DME/DME RNP-0.3 NA” and other related chart notes in this paragraph. Added requirement to specify the applicable navigation specification (NAVSPEC) which will appear in the PBN requirements box.
(15) Paragraph 4-6-10.f. Added guidance to clarify that the lowest RNP value is what is charted for situations where there is more than one that is less than the standard value.
g. Chapter 5. Paragraph 5-2-3.c. Editorial change made to support changes made to Form 8260-9 that now contains a “Part D” dedicated to “airspace.”
h. Chapter 8.
(1) Due to the changes needed to support the changeover to the “report format” for Forms 8260-3/4/5/7A, and the removal of Form 8260-10, numerous changes involving the rearrangement of sentences and paragraphs has been made. Changes made that are significantly different from previous versions of this order are noted below.
(2) Paragraph 8-2-5.e. Removed “En route obstacle clearance criteria apply to feeder routes”; this is addressed in Order 8260.3.
(3) Paragraph 8-3-2.a(2). Editorial change.
h. Chapter 8. › (20) Paragraph 8-6-2.g(1). Updated source for touchdown zone elevation…
(4) Paragraph 8-3-2.a(3). Added “ILS glideslope angle changes” to conditions when “hard dates” can be used.
(5) Paragraph 8-3-3. Updated paragraphs to support new forms formatting.
(6) Paragraph 8-3-4. Aeronautical Information Services, Instrument Flight Procedures Team, responsibilities uniquely identified throughout this paragraph.
(7) Paragraph 8-3-4.b(1). Heliport and airport ID added to text since they will now be entered on the new 8260-3/4/5/7A forms and removed table 8-3-1 the authority to use the P-NOTAM capability for these changes.
(8) Paragraph 8-3-5. Editorial change.
(9) Paragraph 8-4-1.h. Expanded guidance to address whom must sign waiver requests for instrument procedures developed by the FAA and non-FAA service providers.
(10) Paragraph 8-5-1.a. Removed “approved” prior to “non-FAA service providers” and added reference to section 2-10.
(11) Paragraph 8-5-2.g(3). Added “Note” to state that Magnetic and True Bearings are not to be entered when only distance measuring equipment (DME) (i.e., no crossing radials) is used for fix make-up.
(12) Paragraph 8-5-2.g(5). Editorial change for clarity.
(13) Paragraph 8-5-2.h(2). Added guidance to include airspace evaluation to the primary area.
(14) Paragraph 8-5-2.h(2)(h). Revised guidance and added a “Note” to ensure the policy is consistent with Order 8260.3, paragraph 17-2-2, that indicates holding patterns are developed to support time or distance and if the holding pattern serves both, two independent entries will be made on the form.
(15) Paragraph 8-5-2.h(2)(h)2 note. Added note to make it clear that the block title “DME” also applies to RNAV holding pattern leg length distance.
(16) Paragraph 8-5-2.h(2)(j)2.A note was added to address using template used for climbin-hold, if applicable.
(17) Paragraph 8-5-2.h(6)(c). Editorial; changed “Fix” to “Holding.”
(18) Paragraph 8-5-2.j(1). Added “Special DP” and “Special IAP.”
(19) Paragraph 8-5-2.k. Added “Special DP,” “Controller High,” “Controller Low,” and deleted Note relating to controller charts.
(20) Paragraph 8-6-2.g(1). Updated source for touchdown zone elevation (TDZE) and provided rounding rules.
h. Chapter 8. › (35) Paragraph 8-6-10.p(1). Removed text regarding vertical descent…
(21) Paragraph 8-6-4.b(3). Deleted requirement to establish a computer navigation fix for dead reckoning segments on conventional instrument approach procedures; this was originally established to accommodate coding of conventional instrument procedures and is no longer required.
(22) Paragraph 8-6-6.d(7). Added “RNAV” reference based on changes made in Order 8260.58.
(23) Paragraph 8-6-6.h(1). Removed the word “must” and made several editorial changes.
(24) Paragraph 8-6-7.b(2). Expanded guidance and example to include maximum holding altitude when a hold in-lieu-of procedure turn is used.
(25) Paragraph 8-6-7.g(3). Added 20:1 surface block to document whether clear or not clear.
(26) Paragraph 8-6-7.h(1). Added example of minimum safe/sector altitude (MSA) based on the airport reference point.
(27) Paragraph 8-6-7.h(5). Added “and altitudes” to sentence for clarity.
(28) Paragraph 8-6-8. Establishes guidance to support a separate section on approach charts dedicated for equipment requirements notes for conventional instrument procedures and performance based navigation as a result of recommendations addressed at the ACF-IPG, per agenda item 13-02-312.
(29) Paragraph 8-6-9.f. A number of comments were received from the Aviation Weather & Aeronautical Services Programs Group, AJM-33, that were accepted regarding the most current policy relating to automated weather systems.
(30) Paragraph 8-6-9.g note. Added “GLS” and “ILS and/or LOC” to exception.
(31) Paragraph 8-6-9.m. Added reference to see Order 8260.3 for additional guidance when Flight Standards approval may be required.
(32) Paragraph 8-6-9.p. Removed “Procedure Not Authorized when Glideslope not available” to support future criteria application that no longer prohibits localizer only operations when conducting precision runway monitor (PRM) operations.
(33) Paragraph 8-6-9.q. Added statement to prohibit publication of localizer minimums on SOIA PRM procedures.
(34) Paragraph 8-6-10.o. Added guidance on documenting block altitudes.
(35) Paragraph 8-6-10.p(1). Removed text regarding vertical descent angle (VDA)/threshold crossing height (TCH) exceptions that is now addressed in Order 8260.3. Consolidated remaining text from subparagraph “(a)” and “(b)” into the main paragraph.
h. Chapter 8. › (50) Paragraphs 1-1-1.a(1) & 1-1-1.a(1). Expanded guidance for clarity;…
(36) Paragraph 8-6-10.q. Removed text at end of the sentence to eliminate ties to paragraph 8-6-4.b(3), that no longer requires a computer navigation fix for dead reckoning segments.
(37) Paragraph 8-6-11.b(4), 8-6-11.b(5), & 8-6-11.b(6). Updated notes to remove use of symbols.
(38) Paragraph 8-6-11.i(3). Removed stipulation when localizer performance (LP) minima will be established; determination will be driven by PBN criteria or as needed and determined through Regional Airspace and Procedures Team (RAPT) process.
(39) Paragraph 8-6-11.k(3). Revised note that applied when reduction of visibility by helicopters is authorized when using Category A minimums on instrument approach procedures.
(40) Paragraph 8-6-11.o(2)(h). Added sample chart note to indicate the potential application for straight-in procedures.
(41) Paragraph 8-6-11.o(6)(d). Changed “Decision Altitude” to read “Altitude specified by Flight Inspection.”
(42) Paragraph 8-6-12. Added statement to ensure FAS Data Block change information is included (requested by Flight Inspection).
(43) Paragraph 8-6-13. Added two “Notes” and made editorial changes to clarify in this paragraph the requirements regarding coordination with affected ATC facilities and that this paragraph also applies to departure procedures.
(44) Paragraph 8-6-13.c. Made several editorial changes for clarity.
(45) Paragraph 8-6-18.a(2). Removed “publication” from the text as it can be considered part of processing.
(46) Paragraph 8-7-1. Added guidance explaining that if the form is used for helicopter procedures, the copter boxes in the upper left portion of the form must be filled out to activate the block headers associated with helicopter procedures.
(47) Paragraph 8-7-1.b(2). Added guidance to support copter point in space (PinS) procedures.
(48) Paragraphs 1-1-1.a(1). Added note to clarify that the height of missed approach surface (HMAS) entry will only appear in the segment pertaining to the missed approach.
(49) Paragraph 1-1-1.a(1). Due to automation advancements and constraints, the last sentence was revised to make repeated coordinate entries as being optional to support programs that auto-populate all data from previous entries.
(50) Paragraphs 1-1-1.a(1) & 1-1-1.a(1). Expanded guidance for clarity; added guidance for use of DTED and DEM assigned accuracy values.
j. Appendix K. › (3) Paragraph 4o.
(51) Paragraph 8-7-1.b(14). Added “raw value” to indicate the data to be entered is before rounding for publication.
(52) Paragraph 8-7-1.b(24). Added guidance to indicate that bearings provided will be in whole degrees.
(53) Paragraph 8-7-1.c(3). Editorial for clarity.
(54) Paragraph 8-7-1.c(9). Added text to include geographical coordinates when adding this information in Part C.
(55) Paragraph 8-7-1.d(13). Added paragraph to support Order 8260.3, section 16-2, requirement to document a reference to the applicable report (e.g., safety study) that allowed for unique operating situations.
(56) Paragraph 8-8-1.d. Added text for clarity and properly document that controlled airspace was considered; i.e., document airspace floor and buffer used.
(57) Paragraph 8-8-1.i. Deleted statement that said “MRA not applicable for low altitude RNAV routes” and editorial change to clarify documentation action involving minimum turning altitudes (MTA).
(58) Paragraph 8-9-9. Added an “Approved By” block and consolidated “Changes and Reasons” blocks.
i. Appendix C.
(1) Paragraph 2a. Added guidance to, when provided, permit use of assigned accuracy values for DTED and DEM postings.
(2) Paragraph 2b(1)(i). Removed all references to World Aeronautical Charts (WACs); i.e., no longer published.
(3) Table 4. Changed accuracy values for “owner marked positions” of obstacles depicted on 1:20,000 and 1:24,000 maps based on recommendation from Aeronautical Information Services’ Obstacles Team manager and the new methods used to verify the placement of these obstacles.
j. Appendix K.
(1) Paragraph 4d note 1. Deleted; Order 8260.58 does not allow LP to support Circling operations.
(2) Paragraph 4i note 2. Deleted; Order 8260.58 does not allow LP to support Circling operations.
(3) Paragraph 4o. Added guidance to indicate that zeros are entered into this block when a TCH will not be established for an LP procedure.
Section 1-1. General › 1-1-6. Effective Date.
(4) Paragraph 4q. Expanded guidance to indicate that zeros are entered into this block when a VDA is not specified for an LP procedure.
(5) Paragraph 4x. Added “For an LP procedure, the vertical alert limit (VAL) must always be entered as zero (00.0)” for clarification.
1-1-6. Effective Date. This order and subsequent changes are effective on the dates shown in the upper left corner of each page. Implementation of changes must commence no later than 24 months from the published effective date. Previous editions may be used until implementation has commenced, not to exceed 24 months from the new effective date.
1-2-2. Flight Technologies and Procedures Division. › b. Flight Operations Branch. This branch is the principal element of…
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). Responsibility includes governing policy and oversight of manual and automated development and maintenance of terminal and en route flight procedures. The executive director has final authority to issue, amend, and terminate rules and regulations relating to instrument procedures, minimum en route altitudes, flight procedures, operational weather minimums, and minimum equipment requirements.
b. Responsibility for the overall management of the Flight Procedures and Airspace Program is vested in the Flight Technologies and Procedures Division. This order is primarily concerned with those offices having direct responsibility for the accomplishment of the Flight Procedures and Airspace Program. The following is a brief description of their activities.
1-2-2. Flight Technologies and Procedures Division.
a. This division is the principal element of the Flight Standards Service governing policies, criteria, and standards for establishing and maintaining terminal and en route flight procedures; for using air navigation facilities, appliances, and systems; and for validation of FAA instrument procedure design software. 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 Branch. This branch 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. This branch develops 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. This branch develops instrument flight operational concepts, policies, standards, criteria, requirements, specifications, and limitations for new and existing aircraft (all categories) and new and existing airborne, ground-based and space-based systems used in instrument flight operations, and develops and issues Form 8260-7B, Special Instrument Procedure Authorization, as required, through the Procedures Review Board (PRB). This branch provides technical representation to International Civil Aviation Organization (ICAO) on matters related to instrument flight operations, and maintains liaison with foreign civil aviation operational and technical authorities to encourage the acceptance of U.S. instrument flight operations standards and to foster standards with a level of safety consonant with those of the United States. In coordination with original equipment manufacturers (OEMs), Aircraft
1-2-2. Flight Technologies and Procedures Division. › f. Flight Procedure Implementation and Oversight Branch. This branch is…
Certification (AIR), and Aircraft Evaluation Groups (AEGs), identifies explicit operational credit for pilots using new-technology products. This branch provides specific Operations Specification (OpsSpec) language and inspector guidance regarding low visibility operations (CAT II/III) procedures and minima.
c. Flight Procedure Standards Branch. This branch is the principal element within the division, with respect to the rulemaking process of the flight procedures program; also with respect to the development, application, and oversight of national policies and directives for the administration of the National Flight Procedures Program; and development of criteria pertinent to the design of instrument flight procedures. This branch serves as the focal point within Flight Standards for all matters relating to airspace, cartographic programs, instrument flight procedure (IFP) Notices to Airmen (NOTAMs), and is the primary interface for industry on matters relating to instrument procedures criteria. The branch assists the Flight Procedure Implementation and Oversight Branch, providing technical advice and assistance to other FAA elements, government agencies, and industry on the interpretation and application of criteria. It analyzes and evaluates execution of flight procedure programs within the FAA to determine compliance with National policy.
d. Flight Operations Simulation Branch. This branch is the principal element within the division which provides 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 simulation and analysis is accomplished through computer modeling, human-in-the-loop observation in flight and air traffic control (ATC) simulators, and/or industry aircraft. This branch manages the Flight Operations Simulation Laboratory comprised of flight simulators and ATC controller stations that can be linked to provide real time pilot/controller interface and data collection to meet the safety studies’ and risk analyses’ data requirements. These simulations are used to support Flight Standards’ offices, ATO, airports, the aviation industry, and FAA executives who seek objective and subjective human factors safety analysis and assessments to enhance flight operations, standards, capacity, and aviation safety within the NAS and international organizations such as ICAO.
e. Flight Systems Laboratory. This branch is the principal element within the division that analyzes and quantifies the levels of risk probabilities associated with the implementation of new, emerging, and modified flight operational concepts and navigation systems. This branch conducts safety studies for client-proposed changes to the NAS or international standards for other Flight Standards’ offices, ATO, airports, the aviation industry, and FAA executives who seek objective safety assessments to improve flight operations, standards, capacity, aviation safety within the NAS, and international organizations such as ICAO. This branch also develops Flight Systems Laboratory tools software applications [RNAV-Pro, RDVA-Pro, and the Engine Out Surface Evaluator (EOSE)] for use in area navigation/required navigation performance (RNAV/RNP) procedure design and implementation.
f. Flight Procedure Implementation and Oversight Branch. This branch is the principal element within the division, with respect to FAA Instrument Flight Procedures and Flight Inspection policy oversight. This branch develops policy and provides oversight of the IFP development process for government and non-FAA Service Providers. This oversight includes clarifying procedure criteria, confirming procedure development data, conducting simulator
g. AWO responsibilities include but are not limited to the following: › (c) Coordinating the AWO portion of assigned foreign instrument…
evaluations, developing policy for flight validation of IFPs, and monitoring validation flights. This branch manages the program for the review and approval of all special IFPs. Also manages the program to review approval/waiver requests of procedure design standards, and functions as the final approving authority for those requests. This branch is responsible for coordinating nongovernment procedure developer NOTAM authority and access to the Federal NOTAM System (FNS) with ATO Mission Support Services, Aeronautical Information Services. This branch develops standards to ensure the orderly processing of all approved IFPs and evaluates the implementation of these standards and practices to determine compliance with established policy. This branch works with other government agencies, the military, aviation industry leaders, and the international community to improve aviation safety by assisting in the IFP development process worldwide.
g. Performance Based Navigation Branch. This branch is the principal element within the division, with respect to performance based navigation across all domains. This branch develops performance based navigation 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. This branch develops and issues Form 8260-7B, as required. In coordination with original equipment manufacturers, AIR, and AEGs, identifies and enunciates explicit operating procedures for pilots using new-technology products. This branch provides guidance to develop OpsSpec requirements (including parts C and H) related performance based navigation, operating minimums, equipment, and training. This branch is responsible for developing concepts, programs, and system requirements necessary to implement performance based navigation 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. Flight Standards All Weather Operations (AWO) manages and directs air carrier, general aviation, and all weather operations programs for a specified local area. Each AWO provides the local implementation of national concepts, policies, standards, systems, procedures, and programs with respect to the operational and flight technical aspects of the all-weather operations program. AWO responsibilities include but are not limited to the following:
(a) Establishing local requirements for and managing distribution o, special instrument approach procedures. Receiving and resolving user/industry comments on new and revised special instrument approach procedures. Executing national programs such as the Required Navigation Performance/Authorization Required (RNP/AR) instrument approach procedure (IAP) program.
(b) Providing technical evaluations in support of local airspace programs to determine the effect on operational safety and visual flight operations. Specific study responsibilities for AWOs are specified in Order JO 7400.2, Procedures for Handling Airspace Matters, and dictate involvement in a broad range of technical evaluations (i.e., determining feasibility for CAT II/III operations utilizing AWO missed approach tool, assessing operational safety for taxiway/runway separation, and configuration relative to a proposed CAT II/III, etc.).
(c) Coordinating the AWO portion of assigned foreign instrument approach procedures programs as specified in Order 8260.31, Foreign Terminal Instrument Procedures (FTIPs).
1-2-3. Air Traffic Organization, Flight Program Operations. › b. Flight Program Operations, Flight Inspection Scheduling is…
(d) Approving CAT II and III operation and coordinating continuity of service assurance with the ATO Service Area. Local focal point for coordinating inter-service Surface Movement Guidance Control System (SMGCS) activities, site inspections, and the approval of the associated SMGCS plan and periodic reviews.
(e) Providing the operational input on matters related to local capacity studies and airport operational safety initiatives.
(f) Performing Obstruction Evaluation and Airport/Airspace Analysis (OE/AAA) evaluations to address the effect of obstacles on visual flight operations and instrument flight operations (e.g., OE studies) relative to AAA studies, assess operational safety and safety of persons and property on the ground in coordination with the Airports division, as necessary.
(g) Review of charted visual flight procedures and RNAV visual flight procedures.
(h) Coordinating with Airports Division in the approval or denial of modifications to airport standards, providing written safety assessment of end-around taxiway (EAT) proposals/use, and declared distance concepts (see Order JO 7400.2).
(i) Providing operational review and comments for Air Traffic Technical Operations Service Area’s submission of a NAS change proposal (NCP), evaluation of new ATC towers and similar ATO projects. This activity includes participation in the associated Safety Risk Management Document (SRMD) analysis and acceptance processes.
(j) Assists in developing the equivalent level of safety for an Aeronautical Information Services originated procedures waiver.
(k) Provides local level support for activities related to non-FAA service providers.
1-2-3. Air Traffic Organization, Flight Program Operations.
a. Flight Program Operations is the principal element directly responsible for the flight inspection of electronic signals-in-space from ground-based navigational aids, and/or flight validation that support aircraft departure, en route, and arrival flight procedures in the NAS. Flight procedures are also evaluated for accuracy, aeronautical data, human factors flyability, and obstacle clearance; this includes the evaluation of avionics database code which represents the IFP in the Flight Management System (FMS). Flight Program Operations supports 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. Flight Program Operations is also responsible for input (when solicited) to the Air Traffic Technical Operations Service Areas Facilities and Equipment (F&E) budget submission with respect to terminal air navigation aids (other than radar) and visual approach aids.
b. Flight Program Operations, Flight Inspection Scheduling is responsible for scheduling flight inspections. Flight Inspection Scheduling maintains liaison with Aeronautical Information Services, as well as other FAA offices, civil and military interests, to ensure consideration of all
(1) The National Flight Data Center (NFDC) is one element within AJV-5… › (a) Publishing the daily National Flight Data Digest (NFDD) and 56-day…
requirements relating to the procedural use of navigation facilities. Flight Inspection Scheduling’s responsibilities include but are not limited to:
(1) Issuing NOTAM D in accordance with Order 8200.1, United States Standard Flight Inspection Manual.
(2) Managing, processing, and coordinating flight inspection procedure packages.
(3) Scheduling special requests for flight inspections.
(4) Maintaining suitable record system reflecting the status of each flight.
(5) Managing the requirements and technology for Flight Inspection Report System, Flight Operations Management System, and Flight Management Daily Flight Log.
(6) Focal point for all PBN Policy and Support Office generated (CSV) files as well as the KSN DME/DME directory.
(7) Providing Flight Inspection Reports (FIR) containing data pertinent to the AIRNAV database and resolving AIRNAV data discrepancies.
(8) Ground evaluation (validation) of coded IFPs.
(9) Initiating and completing investigative remedial action with respect to any deficiency or reported hazard, including restrictions or emergency revisions to procedures.
c. Aircraft Operations is the principal element within Flight Program Operations responsible for flight inspection of navigation aids and instrument flight procedures in support of the NAS. Flight Program Operations has multiple facilities that support the flight inspection mission.
1-2-4. Air Traffic Organization, Mission Support Services (AJV-0).
a. Aeronautical Information Services (AJV-5) is directly responsible for managing the agency’s program to provide Aeronautical Information Services to ensure the flow of information necessary for safety, regularity, and efficiency of air navigation. This office is charged with the responsibility for collecting, collating, validating, 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) The National Flight Data Center (NFDC) is one element within AJV-5 with respect to maintaining the National Airspace System Resources (NASR) database and for disseminating information relating to the NAS. NFDC is also responsible for maintaining proposed data within the AIRNAV database for the development of instrument flight procedures. NFDC 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
(2) Aeronautical Information Services is the principal element… › (d) Managing the verification/validation of airport survey safety…
NAS. Respective changes are also published in Order JO 7340.2, Contractions, and Order JO 7350.8, Location Identifiers.
(b) Conducting pre-publication review of aeronautical data contained in standard instrument approach and departure procedures, standard terminal arrivals, standard instrument departures, military training routes, navigational aids, airport data, and airspace changes submitted for action, and to identify and correct items in non-conformance with applicable directives.
(c) Validating submitted data with the NASR Database and resolving contradictions.
(d) Managing the development and assignment of five-letter fix names and navigational aid (NAVAID)/airport identifiers.
(e) Issuing, on a predetermined schedule, amendments to 14 CFR part 95.
(f) Maintaining copies of 8260- and 7100-series forms that support public use standard instrument approach procedures (SIAPs), fixes, airways, standard terminal arrival routes (STARs), and departure procedures (DPs).
(2) Aeronautical Information Services is the principal element responsible for developing, directing, and recommending national policy and criteria for aeronautical information. This group serves as the Mission Support Services focal point for developing and managing Geographic Information Systems for the NAS. They are also responsible for collecting, validating, 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 AIM and Aeronautical Information Services through the ICAO.
(b) Collecting, validating, managing, and disseminating as-built obstacle data reported under 14 CFR part 77.
1. Providing the publically-available Digital Obstacle File (DOF), which contains a record of all as-built man-made obstructions that effect domestic aeronautical charting products.
2. Providing Obstacle Repository System (ORS) data to other FAA offices on a timely basis.
(c) Verifying source data for as-built obstacles and assigning accuracy codes that reflect the reliability of the reported obstacle's vertical height and horizontal position.
(d) Managing the verification/validation of airport survey safety critical data.
1-2-4. Air Traffic Organization, Mission Support Services (AJV-0). › c. Air Traffic Standards & Procedures Directorate (AJV-8) provides…
(e) Managing the requirements and technology to support database needs and infrastructure.
b. Aeronautical Information Services (AJV-5) is also responsible for the development, maintenance, quality assurance, and technical approval of public-use flight procedures, production, and distribution of aeronautical charts and related publications and products. Responsibilities include but are not limited to the following:
(1) Development, publication, and maintenance of SIAPs.
(2) Development, publication, and maintenance of obstacle departure procedures (ODPs) and standard instrument departure procedures (SIDs). Development and maintenance of diverse vector areas (DVA).
(3) Development, publication, and maintenance of Air Traffic Service (ATS) routes.
(4) Review and publication of STAR Airport diagrams and special graphics.
(5) Responsible for quality assurance of items produced by Aeronautical Information Services.
(6) Operations support, as requested, for NAS-related products.
(7) Selecting and evaluating source data for final chart compilation.
(8) Validating geographical positions, distances, and bearings of items produced by Aeronautical Information Services.
(9) Maintaining liaison with elements of FAA to support safe and accurate portrayal of charting data.
(10) Providing civilian charts in support of military requirements.
(11) Providing international charting support to selected foreign countries.
(12) Establishing procedures to ensure operational data are included in the NASR database.
(13) Analyzing obstruction evaluations to determine the effects on current and planned instrument flight operations, minimums, and/or flight altitudes of all civil, joint-use, and U.S. Army instrument procedures in accordance with current policy.
(14) Promulgating SIAPs, ODPs, and permanent FDC NOTAMs relating to IFPs with assigned effective dates in a bi-weekly transmittal letter and completing necessary requirements for publication in 14 CFR part 97.
c. Air Traffic Standards & Procedures Directorate (AJV-8) provides support to air traffic operations through policy, procedures, separation standards, equipment, software, and other operations related to air traffic activities across the NAS. AJV-8 serves as the primary point of
d. Service Center, Operational Support Group, Flight Procedures Teams… › (8) Evaluating regional airport and airspace changes for impact on…
contact for the Service Areas, Service Centers and field facilities for Terminal, En Route and Oceanic/Offshore operations, standards, and procedures issues. AJV-8 has the following responsibilities regarding ATC policies, standards, and procedures:
(1) Develop and maintain procedural changes to the NAS in support of new systems or new technologies, or capacity and efficiency improvements, or for the purposes of risk mitigation. These procedural changes are normally accomplished by creating or revising an existing air traffic order.
(2) Effectuate NAS changes through the document change process, issuance of a notice, or the creation of a new air traffic order.
(3) Assess and approve Air Traffic Procedural Waivers, including waivers to separation minima as defined Order 1100.161, Air Traffic Oversight, paragraph 4.2.d.3.
(4) Prepare air traffic procedural interpretations.
(5) Assess and approve letters of authorization for airshows and fly-ins and other procedures in accordance with existing orders.
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) Serving as Chairperson of the Regional Airspace and Procedures Team (RAPT) under Order 8260.43, Flight Procedure Management Program.
(3) Coordinating requests for new instrument procedures service with the respective Air Traffic Service Area and other concerned offices, and conducting instrument procedures feasibility studies.
(4) 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.
(5) Planning and coordinating new or relocated NAS facilities.
(6) Coordinating with applicable Air Traffic Service Areas to select a charting date consistent with priorities and workload when a component of the NAS is to be commissioned, de-commissioned, or altered.
(7) Coordinating the input for the planning and development of regional and Air Traffic Service Area F&E budget submissions and programming actions.
(8) Evaluating regional airport and airspace changes for impact on instrument flight procedures.
(9) Determining the necessity for environmental impact studies as required by current policy.
Section 1-2. Responsibilities › 1-2-5. Individual.
(10) Acting as the focal point for flight inspection issues within the region.
1-2-5. Individual. Personnel working within the Flight Procedures Program are responsible for maintaining professional knowledge in a technical, complex, and specialized field, and for the application of the knowledge to assure safety and practicality in air navigation. Where directives are deficient, each individual must take the initiative to seek an acceptable method of resolution and to inform the responsible office of any recommended change to policy, procedures, etc. that is cost beneficial and/or provides increased operational safety.
THIS PAGE IS INTENTIONALLY LEFT BLANK
a. Operation of airport lighting and visual aids is contained in the… › (1) Order JO 7110.10, Flight Services.
Chapter 2. General Procedures
Section 2-1. General
Note: This chapter provides guidelines and procedures that are common to all instrument flight procedures. Specific guidelines and procedures for en route and terminal instrument flight procedures are contained in chapters 3 and 4, respectively.
2-1-1. Requests for public-use Instrument Flight Procedures (IFPs).
a. Requests for approval and/or establishment of instrument flight procedures may originate from many different sources (see Order 8260.43). It may be a request from a state, city, airport manager, or an individual. It may also be from an air carrier, air taxi, military, commercial operator, ATC, or Flight Standards’ personnel. General information on the lifecycle process associated with IFPs can be found in appendix M.
b. Requirements for approval of IFPs are contained in Order 8260.3, chapter 1.
c. Procedures with specific effective dates, and other urgent projects, will be assigned priorities by Aeronautical Information Services. All other projects will be processed as workload permits, by Aeronautical Information Services in order of receipt.
2-1-2. Air Traffic Letters of Agreement (LOAs). When LOAs affect or include flight procedures, they must be coordinated between ATC facilities and Aeronautical Information Services.
a. When these letters are received, Aeronautical Information Services must review them to ensure compatibility with published or planned flight procedures.
b. Copies of LOAs received in Aeronautical Information Services must be made a part of the procedure files, to serve as a reference when developing or amending flight procedures.
c. When the terms of the LOAs and flight procedures are not compatible, or if it is determined that the terms do not comply with criteria, Aeronautical Information Services must return the LOAs to the ATC facility with a memorandum that explains the findings. When appropriate and practical, consideration should be given to adjusting the procedures to accommodate the terms of the agreement.
d. Normally, an LOA is an agreement between two or more ATC facilities. Unless Aeronautical Information Services is a party to the agreement, it is not a signatory and does not approve or disapprove the agreement.
2-1-3. Airport lighting and visual aids.
a. Operation of airport lighting and visual aids is contained in the following orders:
(1) Order JO 7110.10, Flight Services.
2-1-3. Airport lighting and visual aids. › c. Refer to appendix B, Flight Procedures References, for other…
(2) Order JO 7110.65, Air Traffic Control.
(3) Order JO 7210.3, Facility Operation and Administration.
b. Installation criteria are contained in Order 6850.2, Visual Guidance Lighting Systems.
c. Refer to appendix B, Flight Procedures References, for other applicable orders and advisory circulars.
2-2-2. Aeronautical charts and publications. › d. Aeronautical Information Services is responsible for the accuracy…
Section 2-2. Aeronautical Charts
2-2-1. Use of maps and charts.
a. Aeronautical Information Services should maintain an adequate supply of current charts, or electronic equivalent, to support the development of instrument procedures within its area of responsibility. For manual application, the largest scale charts available should be used to develop final, circling, and the first part of the missed approach segment. For precision approach procedures, survey information or an equivalent plan and profile chart is recommended for use. For all approach procedures, the 7 1/2 and 15-minute quadrangle topographic charts (Quads) produced by the U.S. Geological Survey provide an excellent source for determining terrain elevation. 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 (DOF), AIRNAV database, Aeronautical Information Services Weekly Obstacle Memo, Digital Terrain Elevation Data (DTED), Digital Elevation Model (DEM), etc., in addition to on-site obstacle assessment evaluations, where necessary. The Sectional Aeronautical Chart (scale 1:500,000) and the visual flight rules (VFR) Terminal Area Chart (scale 1:250,000) are good supporting source documents; however, they may not depict all current information because of the extended charting cycle.
b. Map requirements for inclusion in a flight inspection package are determined by Flight Program Operations (see Order JO 8200.44, Coordination of Flight Inspection Procedure Packages).
2-2-2. Aeronautical charts and publications.
a. Aeronautical charts used for air navigation are generally of two groups: VFR charts and IFR charts. The VFR charts are the Sectional charts, VFR Terminal Area charts, and the visual navigation chart. IFR charts include the En Route Low and High Altitude and Area charts as well as the Terminal Procedures Publication (TPP), which includes SIAP, textual and graphic DP, STAR, and Charted Visual Flight Procedure charts.
b. The primary publication, which contains 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 U.S. nonscheduled operators, business, and private aviators flying outside of the U.S. is the Aeronautical Information Publication (AIP). Flight Technologies and Procedures Division’s personnel should conduct periodic surveillance of the AIM and AIP to verify the accuracy and appropriateness of the information. AIM and AIP discrepancies and errors should be forwarded to the Air Traffic Procedures, Process Support Group (AJV-81).
c. Aeronautical Information Services personnel should monitor charts or publications released by the FAA that provide informative material, recommended or mandatory, to determine that safe operating practices and conditions are accurately described for aviation users.
d. Aeronautical Information Services is responsible for the accuracy and completeness of flight data submitted by that office for publication. Procedure specialists should review the resulting published U.S. Government charts to ensure correct portrayal. Aeronautica 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. Any FAA personnel who find or are notified of aeronautical chart…
e. Aeronautical Information Services is responsible for ensuring that U.S. Government Aeronautical Charts conform to Interagency Air Cartographic Committee (IACC) specifications.
f. The National Flight Data Center (NFDC) serves as the focal point for questions regarding other non-procedural data; e.g., airport/runway data, frequencies, etc. NFDC will resolve questions through the appropriate data source steward.
g. Any FAA personnel who find or are notified of aeronautical chart discrepancies and/or errors should send notification to [email protected].
Section 2-3. Environmental Requirements › 2-3-2. Environmental impacts.
Section 2-3. Environmental Requirements
2-3-1. Noise abatement. The establishment of noise abatement procedures is the responsibility of the ATO. However, the Flight Standards Service has an input from an aircraft operational standpoint. These procedures should be coordinated between the appropriate AWO and the OSG-FPT. The AWO must review noise abatement procedures for aircraft performance characteristics and operational safety considerations. The OSG-FPT must review these procedures for practicality and adherence with applicable criteria, and has the primary responsibility for resolving conflicts between IFR procedures and existing or proposed noise abatement procedures.
2-3-2. Environmental impacts. Compliance with the following directives: Order 1050.1, Policies and Procedures for Considering Environmental Impacts, and Order JO 7400.2, chapter 32 is required to meet the environmental compliance requirements of the Agency under the National Environmental Policy Act (NEPA).
2-4-2. ATC usable distance and altitude limitations. › a. DME/VOR/VORTAC/TACAN.
Section 2-4. Facility Utilization and Monitoring
2-4-1. Frequency Service Volumes. In establishing instrument flight procedures, consideration must be given to the type of navigation facilities available and to their limitations.
a. All electronic navigation facilities are installed in accordance with frequency separation specified in distances and altitudes. Specific frequency protected service volumes are contained in Order 6050.32, Spectrum Management Regulations and Procedures Manual. The Regional Frequency Management Officer (RFMO) primarily uses this order. Order 6050.32 also contains information to facilitate understanding and coordination of operational considerations associated with expanded service volumes.
b. Operational service volume includes the standard service volume (SSV) and expanded service volumes (ESVs). The operational service volume must not extend outside the frequency protected service volume on any radial, at any distance, or at any altitude.
2-4-2. ATC usable distance and altitude limitations. When flight procedures are developed which reach outside of the standard service volumes listed below, the submission and processing of an ESV Request, is mandatory. Flight check measurements must not be used as a substitute for an approved ESV [see figure 2-4-1, figure 2-4-2, and figure 2-4-3].
a. DME/VOR/VORTAC/TACAN.
Facility
Class
Usable Height Above
Facility
Usable Distance
(NM) T 12000 and below 25 L 18000 and below 40 H 60000-45000 100 Below 45000-18000 130 Below 18000-14500 100 Below 14500 40
Note: All elevations shown are with respect to the station’s site elevation.
Figure 2-4-1. Standard High Altitude Service Volume
Figure 2-4-2. Standard Low Altitude Service Volume
Figure 2-4-3. Standard Terminal Service Volume
Height Above
b. Nondirectional beacon (NDB).
Facility
Class
Height Above
Facility
Distance (Nautical Miles)
COMLO Note: Low frequency 15 MH beacons have no 25 H standard height 50 HH limitations 75
Note: The COMLO is an NDB of low power, strategically located on an instrument landing system (ILS) approach path to provide L/MF azimuth guidance to an airport, in addition to the more precise guidance of the ILS LOC. COMLOs are normally collocated with ILS Outer Markers (OM) and Middle Markers (MM), and referred to as “LOM” and “LMM,” respectively.
c. Instrument Landing System (ILS).
Facility Height Above Facility Distance (Nautical
Miles) Localizer (FC) 4500 and below 18 Localizer (BC) 4500 and below 18 Glide Slope (2°-4°) varies with angle 10
2-4-3. Requests for Expanded Service Volumes.
a. When ATC requires use of NAVAIDs outside (i.e., laterally and/or vertically) the limitations cited in paragraphs 2-4-2.a through 2-4-2.d, ATC submits an ESV request, with a description of the flight procedure requiring it. The Frequency Management Officer (FMO) first reviews this request. The FMO applies the criteria contained in Order 6050.32. If the FMO disapproves the request, it is returned to the originator without further action. FMO approved or restricted ESVs are then reviewed by Aeronautical Information Services.
b. Aeronautical Information Services is responsible for accuracy, clarity, and practicality of the data. If the ESV request is unclear, or if the FMO approved request has restrictions or restrictive comments, it may be necessary to coordinate changes with the FMO and/or the originating office. FAA flight inspection determines if the facility supports the procedure. The flight inspector may utilize facility files and approve the ESV based on supporting data, providing the data was taken within the last five years. If sufficient data are not available, accomplish a flight check of the procedure before Aeronautical Information Services approval.
c. The procedures specialist when developing an instrument procedure may determine a requirement for an ESV; e.g., the instrument procedure is proposed beyond SSV. In this case, the procedures specialist processes an ESV electronically via the Expanded Service Volume Management System (ESVMS website) to obtain the FMO and, in turn, flight inspection approval. An ESV request must not be used as a substitute for proper instrument procedure design.
d. Facility rotation due to magnetic variation change should have no effect on coverage; however, radials used will change. Aeronautical Information Services initiates a change action via the spectrum management web site (ESVMS) on the date the rotation is effective.
e. For holding patterns, process an ESV request for the holding fix. Describe holding fix by radial, distance, altitude.
b. Monitoring categories. Navigational facilities are classified in… › (4) Category 4.
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-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-7. Utilization of 75 MHz markers. › d. Breaks in MEAs. The 75 MHz markers must not be used to define the…
2-4-6. Utilization of monitoring categories.
a. Category 1 facilities may be used for instrument flight procedures without limitation.
b. Category 2 is a temporary condition not considered in instrument procedure development. The ATO is responsible for issuing NOTAMs on these out-of-service facilities when pilot reports indicate facility malfunction.
c. Category 3 facilities may be used in accordance with the following limitations:
(1) Alternate minimums must not be authorized if facility provides final approach course (FAC) guidance; is required for procedure entry; is used to define the final approach fix (FAF); or is used to provide missed approach guidance [see also paragraph 8-6-11.b].
(2) Consider denying or adjusting terminal routes that require reception of succeeding category 3 facilities to avoid obstacles.
(3) Dogleg airways or routes must not be predicated on these facilities.
(4) Navigational fixes developed from crossing radials of category 3 facilities must not be used to break a MEA to higher MEA (can be used as a break to a lower MEA).
d. Category 4 facilities may be used in accordance with the following limitations:
(1) Alternate minimums may be authorized when the remote status indicator is located in an FAA ATC facility, and then only during periods the control point is attended.
(2) If the control point is other than an FAA facility, a written agreement must exist whereby an ATC facility is notified of indicated changes in facility status.
Note: Failure of this category 4 status indicator or closure of the control point will render the facility and the approach procedure unusable during the outage.
2-4-7. Utilization of 75 MHz markers. The 75 MHz markers may be used as the sole source of identification with the following limitations:
a. Missed approach point (MAP). Markers may be authorized as missed approach points for nonprecision approaches, provided a remote status indicator (RSI) is installed at an ATC facility.
b. Final approach fix. As a non-precise final approach fix, the marker must be monitored if alternate minimums are authorized. The marker need not have an RSI if collocated with a compass locator with a remote status indicator.
c. Course reversals. Procedure turns and holding must not be authorized from a 75 MHz marker.
d. Breaks in MEAs. The 75 MHz markers must not be used to define the point where an en route climb to a higher altitude is required (may be used as a break to a lower altitude).
2-4-7. Utilization of 75 MHz markers. › e. DP turn points. The 75 MHz markers must not be used to identify turn…
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.
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. Aeronautical Information Services. › (1) Publish isogonic lines or segments on appropriate aeronautical…
a. Background. The National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), and the National Geodetic Survey (NGS), for all areas of the U.S. and its territories for application to navigation charts and maps, is the source for MV information and tools for establishing MV. Changing values for MV are tabulated and published on a five-year epoch basis; e.g., 00, 05, 10, 15, 20, etc. In order to assist in stabilizing the NAS, a fixed value of MV is assigned to each NAVAID and airport as the MV of record. This value is applied to true directions to obtain the magnetic values for radials, courses, bearings, and headings published in instrument flight procedures. Periodic updating of the MV assigned to navigation facilities is required to maintain reasonable proximity of alignment with the earth’s ever-changing magnetic field. It is possible that the magnetic course displayed by the aircraft's RNAV system is different than the magnetic course portrayed on the IFP chart.
Note: RNAV systems, unlike IFP designs, generally apply the MV value stored in their navigational database, though other values are sometimes applied. As such, it is entirely possible that the MV applied by the RNAV system is different than the MV used by the procedure designer when the IFP chart was last updated. Thus, the magnetic course displayed by the RNAV system may not match the magnetic course charted on the IFP plate. Despite this difference, an RNAV system should still navigate properly as these systems use true north for navigation and only display magnetic course for pilot reference.
b. Participating offices. Management and control of epoch year MV values require action by the following offices:
(1) Aeronautical Information Services.
(2) Military organizations.
(3) National Flight Data Center.
(4) Western, Central, and Eastern Technical Operations.
(5) Western, Central, and Eastern OSG-FPTs.
(6) Regional Airports Divisions.
2-5-2. Responsibilities.
a. Aeronautical Information Services.
(1) Publish isogonic lines or segments on appropriate aeronautical charts based on current epoch year values.
(2) Revise en route aeronautical charts and Chart Supplements to reflect revised MV assignments to navigation facilities in accordance with information published in the NFDD.
a. Aeronautical Information Services. › (10) Amend instrument flight procedures as required, predicated on…
(3) Revise en route charts to apply yearly MV change values to RNAV (“Q” and “T”) route Magnetic Reference Bearings (MRB) during the first airspace charting cycle of each calendar year.
(4) Function as the focal point for all information relating to application of MV to the following elements of the NAS: NAVAIDs, airports, instrument flight procedures; and for coordination and liaison between Aeronautical Information Services and the applicable Air Traffic Service Center OSG-FPTs.
(5) Function as the focal point for FAA and all NAS Facilities Flight Inspection coordination. Terminal facilities (other than VOR, VOR/DME, TACAN, VORTAC, and radar systems) do not require flight inspection of MV changes.
(6) Determine whether NOTAM action is necessary when required procedural adjustment action or MV change is not accomplished by the effective date of amended instrument procedures or revised en route charts.
(7) For FAA and all NAS facilities, assign and maintain MVs of record for navigational facilities and airports in whole degree increments. MVs of record are available in the AIRNAV facility database. For new or relocated facilities, and new or revised instrument procedures, apply the appropriate MV. Analyze each facility identified as a candidate for revised MV assignment to determine if facility rotation and/or re-designation of radials are required.
(8) Establish a process to record the assigned magnetic variation and epoch year of NAVAIDs and airports by geographical location and the projected MV for the next epoch year. The process must also include the ability to identify those candidate navigational aids and airports with a difference of two degrees or more between the MV of record and the nearest future epoch year value.
(9) Notify NFDC 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.
b. United States Air Force (USAF). › (2) Function as the focal point for USAF non-NAS facility flight…
(11) VOR, VOR/DME, and VORTAC facilities supporting the en route structure (which may or may not have instrument procedures predicated on them):
(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 NFDC.
(b) Coordinate changes with the OSG-FPT (OSG-FPTs are expected to coordinate with the applicable ARTCC and/or approach control) in an attempt to eliminate routes, fixes, and instrument procedures that are no longer required.
(12) NAVAIDs not supporting en route structure:
(a) Initiate implementation of the nearest future epoch year MV in accordance with paragraph 2-5-3.a, whenever any instrument procedure is established or amended. The nearest future epoch year MV will become effective concurrent with publication of the amendment [see paragraphs 8-6-2.l and 8-6-10.l].
(b) Amend and process multiple instrument procedures to simultaneously become effective concurrent with the instrument procedure specified in the MV change notification to NFDC.
(c) Submit revisions of all affected fixes with the instrument procedure(s). Change ESVs.
(d) Amend radar procedures when the airport MV of record is changed.
(13) Army facilities.
(a) Accomplish MV changes for U.S. Army facilities in the same manner as for civil facilities; however, obtain the installation commander’s prior approval.
(b) Notify the appropriate military representatives, in writing, when the need to change the MV of other military facilities is identified.
b. United States Air Force (USAF).
(1) Function as the focal point for all USAF applications of MV for USAF facilities within and outside the NAS to include; NAVAIDs, airports, instrument flight procedures.
(2) Function as the focal point for USAF non-NAS facility flight inspection requirements and coordination. Terminal facilities (other than VOR, VOR/DME, TACAN, VORTAC, and radar systems) do not require flight inspection of MV changes.
(9) USAF navigational facilities not within the NAS: › (a) Initiate implementation of the nearest future epoch year MV, as per…
(3) Determine whether NOTAM action is necessary when required procedural adjustment action or MV change is not accomplished by the effective date of amended instrument procedures or revised en route charts.
(4) Assign and maintain MVs of record for USAF non-NAS navigational facilities and airports in whole degree increments. For new or relocated facilities, and for new or revised instrument procedures, apply the appropriate MV. Analyze each facility identified as a candidate for revised MV assignment to determine if facility rotation and/or re-designation of radials are required.
(5) Maintain a listing/record of USAF navigational aids and airports by geographical location. Indicate the currently assigned MV of record and the projected MV for the next epoch year. For the purpose of planning and implementation, maintain a current listing of those candidate navigational aids and airports with a difference of two degrees or more between the MV of record and the nearest future epoch year value.
(6) Notify Aeronautical Information Services of changes to USAF non-NAS facilities assigned MV and the effective date of those changes in order to generate a letter to NFDC for publication in the NFDD; notify other concerned offices having related responsibilities to ensure timely implementation of necessary actions. The effective date selected must allow sufficient time for procedures processing in accordance with established schedules. MV changes, which affect only terminal instrument procedures, must have an effective date concurrent with publication of a specific procedural amendment.
(7) Amend instrument flight procedures as required, predicated on navigational aids or airports undergoing a change of MV of record. Conduct a thorough survey to determine the full impact the MV change will have on any instrument procedure. Such surveys must include high and low altitude airways/jet routes, direct routes, air carrier off-airway routes, fixes in both high and low altitude structures, terminal routes and fixes, ODPs, SIDs, STARs, ESV’s, and any other application to instrument flight procedures. Use the MV of record (or as officially changed) to develop instrument flight procedures - regardless of the MV shown on the airport diagram or similar product being used.
(8) USAF navigational facilities within the NAS:
(a) Maintain official listing of USAF facilities that are part of the NAS.
(b) Notify Aeronautical Information Services when MV changes are required. Allow sufficient time for modification of FAA fixes and IAPs as necessary.
(9) USAF navigational facilities not within the NAS:
(a) Initiate implementation of the nearest future epoch year MV, as per paragraph 2-5-3.a, whenever any instrument procedure is established or amended. The nearest future epoch year MV must become effective concurrent with publication of the amendment [see paragraphs 8-6-2.l and 8-6-10.l].
d. OSG-FPT. › (1) Notify Aeronautical Information Services of MV changes when…
(b) Amend and process multiple instrument procedures to simultaneously become effective concurrent with the instrument procedure specified in the MV change notification to NFDC.
(c) Submit revisions of all affected fixes with the instrument procedure(s). Change ESVs, as required.
(d) Amend all procedures as, required, when the airport MV of record is changed.
c. United States Navy.
(1) Contact Aeronautical Information Services to obtain the MV of record or MV assignments for new or relocated facilities to be applied to navigational aids or airports under U.S. Navy jurisdiction.
(2) Coordinate with Aeronautical Information Services to determine impact of MV changes for both military and public facilities.
(3) U.S. Navy flight procedure development work generally follows the same requirements as Aeronautical Information Services’ flight procedure development work as outlined in paragraphs 2-5-2.b(3) through 2-5-2.b(9). Aeronautical Information Services will remain the office of primary responsibility for paragraphs 2-5-2.b(1), 2-5-2.b(2), 2-5-2.b(4), and 2-5-2.b(5) functions.
(4) Notify Aeronautical Information Services of changes to U.S. Navy, non-NAS facilities, assigned MV and the effective date of those changes in order to allow Aeronautical Information Services to publish them in the NFDD; notify other concerned offices having related responsibilities to ensure timely implementation of necessary actions. The effective date selected must allow sufficient time for procedures processing in accordance with established schedules. MV changes, which affect only terminal instrument procedures, must have an effective date concurrent with publication of a specific procedural amendment.
(5) U.S. Navy navigational facilities within the NAS:
(a) Maintain official listing of U.S. Navy facilities that are part of the NAS.
(b) Notify Aeronautical Information Services when MV changes are required. Allow sufficient time for modification of FAA fixes and IAPs as necessary. National Flight Data Center, when notified by Aeronautical Information Services of any change to MV of Record, publish a notice of change in the NFDD. 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-5-3. Guidelines for Magnetic Variation (MV) revisions. › b. Standard MV limits for airports and NAVAIDs. When the difference…
(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.
f. Regional Airports Division/Airports District Office (ADO). Coordinate with the applicable OSG-FPT prior to establishing or revising runway designator numbers for an airport having one or more instrument approach or departure procedures, to determine the appropriate MV to be applied to the runway true bearing. Determination of the runway designator number should be a matter of joint agreement with Aeronautical Information Services, and be accomplished sufficiently in advance to allow for procedural amendments. Take appropriate NOTAM action if repainting of an affected runway has not been accomplished on the required date.
2-5-3. Guidelines for Magnetic Variation (MV) revisions. The identification and selection of NAVAIDs or airports, as candidates for revision of MV of record require careful consideration and evaluation of a number of factors - as the impact of MV changes can be considerable. The applicable Air Traffic Service Area Office may have to initiate or revise published air traffic procedures; the Technical Operations Service (AJW-0) is directly involved in NAVAIDs/radar rotations and requires proper coordination. The Airports Division, or appropriate military authority, may have to arrange for repainting of runway designator numbers [see paragraph 8-3- 4.b(5)].
Note: Guidelines pertaining to runway designation marking relative to magnetic changes can be found in AC 150/5340-1, Standards for Airport Markings.
a. MV versus epoch year value. The NOAA World Magnetic Model (WMM) is used to determine the current MV at a location and to calculate the future MV for use in procedure design and publication. The model estimates the MV at any location and day within the five-year validity window of the model. For example, the WMM released in December 2009 provides MV values for all locations for January 1, 2010 through December 31, 2014. The nearest future epoch year value calculated using that model would be specified as 2015, and the MV based on the December 31, 2014 value, except as indicated in paragraph 2-5-3.c. The assigned MV is listed as using the 2015 epoch year even when the value is associated with a date earlier in the validity period of the model.
b. Standard MV limits for airports and NAVAIDs. When the difference between the MV of record and the nearest future epoch year value of any NAVAID, or the assigned airport MV of record, will exceed three (3.0) degrees [five (5.0) degrees for VORs and VORTACs], the MV of record must be changed to the nearest future epoch year value and applied to airport reference point (ARP) and all on-airport NAVAIDs. Consider implementing the change earlier in cases where revisions of multiple procedures are required for other reasons, such as when other nearby airports are being updated or when weather, or other factors, would preclude the change being accomplished at the time the MV would actually exceed three (3.0) degrees. Off-airport
(2) RNAV. › (a) Instrument approach procedures (IAPs)/DPs/STARs, including GLS.
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 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 locations with SA CAT II or CAT II/III instrument procedures, 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. At airports with SA CAT II or CAT II/III instrument procedures, the one-degree 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 three (3.0) degrees [five (5.0) degrees for VORs and VORTACs] from the airport MV of record. The difference between the “on airport” VOR or NDB and ILS or GLS MV must not exceed four (4.0) degrees. Larger differences may cause issues for avionics used to fly coupled and autoland approaches.
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 Regional Airspace and Procedures Team (RAPT). 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
g. Standard rules for applying MV to true radials, bearings, courses,… › (3) Diverse Vector Area (DVA).
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. Some aircraft navigation systems use a “reference NAVAID” for obtaining MV information based on course (Cx) leg types and track from fixes (Fx) leg types. For IAPs, specify in the database record [for RNAV Departure Procedures, specify in the “Remarks” section of Form 8260-15C, Departure (Data Record)], a NAVAID that has the same assigned MV as the airport MV. For STARs, see paragraphs 4-5-3 and 4-5-4 for documentation requirements.
(b) Holding on RNAV IAPs/DPs/STARs. To determine the magnetic track/course, apply the published MV of the aerodrome, or the en route VOR or NDB assigned variation when proceeding “to” the NAVAID used as part of a procedure/holding pattern fix to the procedure true track/course.
(c) Holding on RNAV routes or stand-alone. For RNAV only holding patterns not associated with an instrument procedure or a VOR or NDB used as the holding fix, determine the MV by using the magnetic declination (variation) for the holding fix latitude/longitude. This information may be calculated using the WMM.
(3) Diverse Vector Area (DVA). Use airport MV of record when defining DVA heading limitations.
Continue reading ↓ 120 of 877 passages shown