Order 8260.19G Flight Procedures and Airspace
This document is cancelled. Cancelled by 8260.19H. Check the official source before relying on it.
Text read by OCR from a scanned file (107 of 514 pages). Check the original, as some words may be misread.
Order 8260.19G
Effective Date:
07/14/15 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 the 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.
John S. Duncan Director, Flight Standards Service
ORDER 8260.19G
Distribution: Electronic Distribution Initiated By: AFS-400
THIS PAGE IS INTENTIONALLY LEFT BLANK
07/14/2015 Order 8260.19G Table of Contents
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-11
Section 1-2. Responsibilities … 1-12
1-2-1. Flight Standards Service (AFS-1) … 1-12 1-2-2. Flight Technologies and Procedures Division (AFS-400) … 1-12 1-2-3. Regional Flight Standards Divisions (AXX-200) … 1-14 1-2-4. Air Traffic Organization, Technical Operations Flight Inspection Services (AJW-3) … 1-15 1-2-5. Air Traffic Organization, Mission Support Services (AJV-0) … 1-16 1-2-6. Individual … 1-19
Section 1-3. Instrument Procedure Development Software Responsibilities … 1-20
1-3-1. Background … 1-20 1-3-2. Flight Procedure Standards Branch’s responsibility … 1-20 1-3-3. Aeronautical Information Services (AJV-5) responsibility … 1-20 1-3-4. Information Technology Shared Service Organization (AIT) … 1-21 1-3-5. Office of Information Services (AMI-1) … 1-22 1-3-6. Office of Assistant Administrator for Information Services (AIO-1) … 1-22 1-3-7. Vice President for Mission Support Services (AJV-0) … 1-22 Chapter 2. General Procedures … 2-1
Section 2-1. General … 2-1
2-1-1. Requests for public-use Instrument Flight Procedures (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 as en route aids … 2-9
i
07/14/2015 Order 8260.19G Table of Contents
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
Section 2-6. Notices to Airmen (NOTAMs) … 2-20
2-6-1. General … 2-20 2-6-2. United States NOTAM system … 2-20 2-6-3. Instrument Flight Procedure NOTAMs … 2-20 2-6-4. FDC NOTAM preparation, review, and transmittal responsibilities … 2-22 2-6-5. Instrument Flight Procedure NOTAMs … 2-25 2-6-6. Chart correction NOTAMs … 2-26 2-6-7. General NOTAM D actions … 2-26 2-6-8. Air Traffic Service Route NOTAMs … 2-28 2-6-9. FDC NOTAMs for Special Instrument Approach Procedures (Specials) … 2-29 2-6-10. NOTAM content … 2-30
Section 2-7. Quality/Standardization of Instrument Flight Procedures … 2-34
2-7-1. AIS action … 2-34 2-7-2. AFS-460 action … 2-34
Section 2-8. Periodic Review of Instrument Flight Procedures … 2-35
2-8-1. General … 2-35 2-8-2. Reviewing organization action … 2-36
Section 2-9. Communications and Weather … 2-38
2-9-1. Communications requirements … 2-38 2-9-2. Use of UNICOM … 2-38 2-9-3. Automatic altimeter setting and weather reporting systems … 2-38
Section 2-10. Navigational Fixes … 2-40
2-10-1. General … 2-40 2-10-2. Reporting points … 2-40 2-10-3. Unplanned holding at designated reporting points … 2-40 2-10-4. Requests for navigational fixes … 2-40 2-10-5. Naming navigational fixes … 2-41 2-10-6. Documenting navigational fixes … 2-43 2-10-7. Correlation of navigational fixes and changeover points … 2-43 2-10-8. Minimum reception altitudes … 2-44 2-10-9. Flight Inspection … 2-44 2-10-10. Maximum authorized altitudes … 2-45
Section 2-11. Obstacle Data … 2-46
2-11-1. General … 2-46 2-11-2. Obstacle application and data sources … 2-46 2-11-3. Obstacle data accuracy standards … 2-46
ii
07/14/2015 Order 8260.19G Table of Contents
2-11-4. Accuracy standards application … 2-48 2-11-5. Controlling obstacles … 2-49 2-11-6. Datums … 2-54
Section 2-12. Waiver of Standards/Approval Requests … 2-55
2-12-1. General … 2-55 2-12-2. Waiver processing … 2-55 2-12-3. Waivers for Special Instrument Approach Procedures … 2-56 2-12-4. Safety Management System (SMS) requirements … 2-56 2-12-5. Periodic review of waivers … 2-57 2-12-6. Cancellation of waivers … 2-57 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 Air-Space 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-10
Section 3-6. New or Revised National Airspace System Routes … 3-11
3-6-1. Definition - Route … 3-11 3-6-2. Coordination procedures … 3-11 3-6-3. Publication of procedural data … 3-11
Section 3-7. Minimum Vectoring Altitude (MVA) and Minimum IFR
Altitude (MIA) Charts … 3-12
iii
07/14/2015 Order 8260.19G Table of Contents
3-7-1. Chart preparation … 3-12 3-7-2. Obstacle clearance … 3-12 3-7-3. Controlled airspace … 3-12 3-7-4. Chart review and approval … 3-12 3-7-5. Emergency Obstruction Video Map (EOVM) … 3-13 Chapter 4. Terminal Procedures … 4-1
Section 4-1. General … 4-1
4-1-1. General … 4-1 4-1-2. Categories of Instrument Approach Procedures … 4-1 4-1-3. Airspace requirements … 4-1 4-1-4. Contractual use of private facilities … 4-2 4-1-5. TERPS application … 4-2 4-1-6. Sidestep maneuvers … 4-3 4-1-7. Temporary displaced threshold procedures … 4-5
Section 4-2. Standard Instrument Approach Procedures (SIAP) … 4-7
4-2-1. General … 4-7 4-2-2. Coordination of Terminal Instrument Procedures … 4-7 4-2-3. Radar Instrument Approach Procedures … 4-7
Section 4-3. Category II and III ILS … 4-8
4-3-1. General … 4-8 4-3-2. Action … 4-9 4-3-3. NOTAM requirements … 4-10
Section 4-4. Departure Procedures (DP) … 4-11
4-4-1. General … 4-11 4-4-2. Diverse Vector Area (DVA) … 4-11
Section 4-5. Standard Terminal Arrival (STAR) … 4-12
4-5-1. General … 4-12 4-5-2. Roles and Responsibilities … 4-18 4-5-3. Preparation of Form 8260-17.1, Standard Terminal Arrival (STAR) … 4-21 4-5-4. Preparation of Form 8260-17.2, STAR (Data Record) … 4-47
Section 4-6. RNAV Procedure Development … 4-57
4-6-1. General … 4-57 4-6-2. RNAV Approach Procedure design … 4-57 4-6-3. Developing RNAV waypoint … 4-59 4-6-4. RNAV leg types … 4-61 4-6-5. RNAV leg type descriptions … 4-61 4-6-6. Final Approach Segment (FAS) data … 4-62 4-6-7. Remote altimeter setting for Baro-VNAV … 4-62 4-6-8. Critical temperature … 4-63 4-6-9. DME/DME screening model … 4-63 4-6-10. Additional documentation with Baro-VNAV (LNAV/VNAV and RNP), GBAS, and/or WAAS Instrument Approach Procedures … 4-63
iv
07/14/2015 Order 8260.19G Table of Contents 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. AIS action … 5-2 5-2-4. Terminal airspace … 5-3
Section 5-3. Airport Airspace Analysis … 5-39
5-3-1. General … 5-39 5-3-2. Service Area OSG-FPT/Flight Standards inputs in establishment of airports and heliports … 5-39 5-3-3. AFS performs the flight safety review of airport proposals to determine whether aircraft operations can be conducted safely considering the proposal’s effect on the safety of persons and property on the ground … 5-39 5-3-4. Service Area OSG-FPT is responsible for evaluation and comment on all airport proposals related to IFR impact … 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. AFS 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
v
07/14/2015 Order 8260.19G Table of Contents
7-2-1. Planning standards … 7-2 7-2-2. Determination of operational benefits/improvements … 7-2
Section 7-3. Safety Analysis … 7-4
7-3-1. Performing a safety analysis … 7-4
Section 7-4. Airway Planning … 7-7
7-4-1. General … 7-7
Section 7-5. Terminal Planning … 7-8
7-5-1. General … 7-8 7-5-2. Requirements for outer compass locators for new ILS installations … 7-8
Section 7-6. Airport Planning … 7-13
7-6-1. General … 7-13
Section 7-7. Private Aid … 7-14
7-7-1. General … 7-14
Section 7-8. Facilities and Equipment (F&E) Support … 7-15
7-8-1. Support … 7-15 Chapter 8. Instrument Approach Procedures Data Transmittal System … 8-1
Section 8-1. General … 8-1
8-1-1. General … 8-1
Section 8-2. FAA Form Use and Preparation … 8-2
8-2-1. Use of FAA Forms … 8-2 8-2-2. FAA Form preparation … 8-2 8-2-3. Course and distance information … 8-3 8-2-4. Communications data … 8-4 8-2-5. Terminal routes general … 8-4 8-2-6. Terminal fixes … 8-8
Section 8-3. Certification, Processing, and Review … 8-10
8-3-1. General … 8-10 8-3-2. Certification and distribution of SIAPs … 8-10 8-3-3. Cancellation/Suspension of Instrument Approach Procedures … 8-12 8-3-4. Revisions to IFPs … 8-12 8-3-5. Processing … 8-17 8-3-6. AIS review of SIAPs and charts … 8-17 8-3-7. AIS action … 8-17
Section 8-4. Flight Procedures Standards Waiver, FAA Form 8260-1 … 8-21
8-4-1. Preparation of Form 8260-1, Flight Procedures Standards Waiver … 8-21
Section 8-5. Radio Fix and Holding Data Record, FAA Form 8260-2 … 8-24
8-5-1. Introduction … 8-24 8-5-2. Preparation of Form 8260-2 … 8-24
Section 8-6. Completion of FAA Forms 8260-3/5 … 8-34
vi
07/14/2015 Order 8260.19G Table of Contents
8-6-1. General … 8-34 8-6-2. Terminal routes … 8-34 8-6-3. Lines 1 through 8 … 8-36 8-6-4. Takeoff and alternate minimums … 8-43 8-6-5. Minimums … 8-43 8-6-6. Notes … 8-55 8-6-7. Missed Approach … 8-63 8-6-8. Additional Flight Data … 8-69 8-6-9. Lower blocks … 8-74
Section 8-7. Standard Instrument Approach Procedure Data Record,
FAA Form 8260-9 … 8-77 8-7-1. Preparation of Form 8260-9 … 8-77
Section 8-8. Completion of FAA Forms 8260-4/7/10 … 8-86
8-8-1. General … 8-86 8-8-2. Form 8260-4, Radar … 8-86 8-8-3. Form 8260-7A and Form 8260-7B … 8-87 8-8-4. Form 8260-10, Continuation Sheet … 8-89
Section 8-9. Terminal Arrival Area (TAA) Design Criteria –
Documentation and Processing … 8-91 8-9-1. Instructions for 8260-series forms … 8-91
Section 8-10. Transmittal of Airways/Route Data Record, FAA Form 8260-16 … 8-96
8-10-1. Preparation of Form 8260-16 … 8-96
Section 8-11. Simultaneous Close Parallel (SCP) and Simultaneous Offset Instrument
Approach (SOIA) Procedure Attention All Users Page (AAUP) … 8-123 8-11-1. Attention All Users Page … 8-123 8-11-2. Site Implementation Team (SIT) … 8-123 8-11-3. AAUP preparation … 8-123 8-11-4. AAUP processing … 8-123 8-11-5. AAUP publication … 8-123 8-11-6. Forms processing … 8-124 8-11-7. Title line … 8-124 8-11-8. Text … 8-124 8-11-9. Administrative information … 8-127 Appendix A. Administrative Information … A-1
1. Distribution … A-1 2. Terms, definitions, and acronyms … A-1 3. Acronyms and abbreviations … A-1 4. Forms … A-7 5. Information update … A-7 Appendix B. Flight Procedures References … B-1
vii
07/14/2015 Order 8260.19G Table of Contents Appendix C. Obstacle Accuracy Standards, Codes, and Sources … C-1
1. United States National Map Accuracy Standards … C-1 2. Accuracy Codes and Sources … C-2 Appendix D. FAA Form 8260-2, Data Worksheet … D-1
Appendix E. Radio Fix and Holding Data Record, FAA Form 8260-2 … E-1
Appendix F. ILS and RNAV Standard Instrument Approach Procedure, FAA Form 8260-3 … F-1
Appendix G. Radar – Standard Instrument Approach Procedure, FAA Form 8260-4 … G-1
Appendix H. Standard Instrument Approach Procedure, FAA Form 8260-5 … H-1
Appendix I. Special Instrument Approach Procedure, FAA Form 8260-7A and Special Instrument Procedure Authorization, FAA Form 8260-7B … I-1
Appendix J. Standard Instrument Approach Procedure, FAA Form 8260-9 … J-1
Appendix K. Standard Instrument Approach Procedure Continuation Sheet, FAA Form 8260-10 … K-1
Appendix L. Final Approach Segment (FAS) Data Block Cyclic Redundancy Check (CRC) Requirements … L-1
Appendix M. Final Approach Segment (FAS) Data Block Cyclic Redundancy Check (CRC) Requirements for Helicopter Operations – RESERVED … M-1
Appendix N. ARINC 424 Database Codes … N-1
1. Waypoint description codes … N-1 2. Waypoint description code definition/description … N-2 Appendix O. Instrument Flight Procedures (IFP) Lifecycle … O-1
1. This appendix consists of “basic” information pertaining to the “lifecycle” of an FAA-developed IFP … O-1 2. Obtaining/meeting operations and/or aircraft approval requirements necessary for using an IFP are the responsibility of the user and not part of an IFP lifecycle … O-1
viii
a. General. › (5) Due to a change in instrument approach procedure naming (i.e.,…
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.
1-1-2. Audience. The primary audience for this order is the Air Traffic Organization (ATO) Mission Support Services (MSS) and all service providers [see appendix A] who have the responsibility to develop instrument flight procedures. The secondary audience includes all other Air Traffic Organizations, Flight Standards headquarters, and regional office Divisions/Branches who have responsibilities related to instrument flight procedures. Additionally, elements in the Department of Defense (DoD) and Department of Homeland Security (DHS) [hereafter referred to as the “military”] may follow the guidance in this order when and where deemed appropriate.
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.19F, Flight Procedures and Airspace, dated 01/09/2014, is canceled.
1-1-5. Explanation of changes. Significant areas of new direction, guidance, policy, and criteria as follows:
a. General.
(1) Revised page numbering method to make it easier to make future page changes.
(2) Changed “AeroNav Products” to “Aeronautical Information Services” throughout entire directive.
(3) Replaced “DoD” with “military,” where applicable, to be consistent with its use in the Code of Federal Regulations.
(4) Editorial changes made to meet Order 1320.1, FAA Directives Management, paragraph formatting requirements.
(5) Due to a change in instrument approach procedure naming (i.e., change 26 to Order 8260.3B, United States Standard for Terminal Instrument Procedures (TERPS), Volume 1, section 6), instrument procedures containing “/DME” in the procedure name have been edited to remove the “/DME” from the procedure name.
d. Chapter 2. › (7) Paragraph 2-6-3Note. Removed; no longer needed.
(6) Due to a change in instrument approach procedure naming (i.e., change 26 to Order 8260.3B, Volume 1, section 6), instrument procedures referring to “VOR/DME RNAV” have been changed to read “RNAV (VOR/DME).”
(7) All references involving Order 8260.3 have been updated to correspond to the publication of Order 8260.3C.
(8) All references involving Order 8260.58, United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design, have been updated to correspond to the publication of Order 8260.58A.
(9) Removed all Department of Commerce, Obstruction Charts (OC) references since these are no longer produced.
b. Table of Contents. Updated to coincide with the pages changed.
c. Chapter 1.
(1) Paragraph 1-2-2.a. Editorial change “requests” to “approval.”
(2) Paragraph 1-2-2.b. Added text at the request of AFS-410.
(3) Paragraph 1-2-2.f. Last sentence, removed reference to “oversight.”
(4) Paragraph 1-2-7. Paragraph deleted; guidance incorporated into Order 8260.60, Special Instrument Procedures, regarding transferring instrument procedure maintenance responsibility.
d. Chapter 2.
(1) Paragraph 2-1-1.b. Edited text and updated reference.
(2) Paragraph 2-4-3.e. Updated paragraph at the request of Flight Inspection, AJW-331, to reflect current practices.
(3) Paragraph 2-5-2.d. Inserted new paragraph to define Operations Support Group- Flight Procedures Team (OSG-FPT) responsibilities when receiving magnetic variation changes from non-FAA service providers for procedures they maintain. Also moved OSG-FPT responsibility from paragraph 2-5-2.a(4) to this paragraph.
(4) Paragraph 2-5-3. Updated Magnetic Variation (MV) guidelines per working group recommendations. Also added heading guidance for Diverse Vector Area application.
(5) Paragraph 2-6-1. Editorial.
(6) Paragraph 2-6-2.a. Revised paragraph to just refer to Order JO 7930.2, Notices to Airmen (NOTAMs).
(7) Paragraph 2-6-3Note. Removed; no longer needed.
d. Chapter 2. › (24) Paragraph 2-6-10.f. Added guidance to show an example of a NOTAM…
(8) Paragraph 2-6-4.a. Added new keyword for Diverse Vector Area (DVA).
(9) Paragraph 2-6-4.b. Removed references to old terms no longer used to describe effective and expiration times; i.e., “WEF,” “WIE,” “UFN,” and “TIL.”
(10) Paragraph 2-6-4.b(2). Example. Editorial.
(11) Paragraph 2-6-4.d(1). Added text to refer to paragraph containing additional responsibilities for Special instrument procedures.
(12) Paragraph 2-6-4.d(3)(a). Removed “Procedures to ensure that all affected ARTCC facilities are provided notification of NOTAMs at the time of submission [see Order 8260.3]” since all ARTCC facilities receive this information by ERIDS or other electronic means.
(13) Paragraph 2-6-4.e. Editorial to change from “NOTAM Entry System” to just “FAA NOTAM system.”
(14) Paragraph 2-6-5.a. Removed statement that restricted NOTAMs to safety related items only.
(15) Paragraph 2-6-5.b. Added statement to refer to paragraph 8-3-4.c and table 8-3-1, for conditions pertaining to IFP NOTAMs when amending an instrument flight procedure.
(16) Paragraph 2-6-5.d. Inserted guidance for STARs; following paragraphs up-lettered.
(17) Paragraph 2-6-7.e(2). Added method in which AIS would receive this information from AFS-400.
(18) Paragraph 2-6-7.g. Editorial change at the request of Flight Inspection, AJW-391.
(19) Paragraph 2-6-8. Deleted last sentence at the request of the NOTAM Policy Group, AJR-B11.
(20) Paragraph 2-6-8.a. Deleted first sentence at the request of the NOTAM Policy Group, AJR-B11.
(21) Paragraphs 2-6-9.c and 2-6-9.d. At the request of Flight Inspection, AJW-391, statement added to notify Flight Inspection of the applicable change/outage.
(22) Paragraph 2-6-10.a. Removed statement that prevented establishing NOTAMs for items that could be published by a routine amendment.
(23) Paragraph 2-6-10.e. Added OE study number to body of NOTAM at the request of AJV-5. Added “DVA” to types of FDC NOTAMS and provided DVA examples.
(24) Paragraph 2-6-10.f. Added guidance to show an example of a NOTAM used when Category D and E minimums must be curtailed due to certain snow depths when informed by Technical Operation.
e. Chapter 3. › (1) Paragraph 3-1-1.b. Updated reference to proper criteria used for…
(25) Paragraph 2-8-2.a. Incorporated “Instrument Flight Procedure Periodic Review Requirements Revised” Memo dated January 28, 2014.
(26) Paragraph 2-10-4.a(5). Added that AIS will coordinate with current OPR before generating the change.
(27) Paragraph 2-10-5.a(4). Clarified fix naming for missed approach point, addressing non-pronounceable fix name and when not to apply CNF naming standards.
(28) Paragraph 2-10-5.a(5). Editorial change and added note to clarify that fix names beginning with the letters “VP” cannot be used on instrument flight procedures.
(29) Paragraph 2-10-8. Added two sentences at the request of Flight Inspection, AJW-331, to ensure MEAs are not lower than the MRA for the fix.
(30) Paragraph 2-11-2. Revised paragraph title to add “application.” Added a 2-11-2.c to address “transitory obstacles.”
(31) Paragraph 2-11-2.b. Added sentence on lack of vertically guided survey may preclude development of a vertically guided procedure.
(32) Paragraph 2-11-4.c. Added reference to Order 8260.58, chapter 4 for LNAV/VNAV final.
(33) Paragraph 2-11-4.d. Revised obstacle accuracy guidance for RNP AR instrument procedures.
(34) Paragraph 2-11-5.b. Added reference to Order 8260.58, chapter 4 for LNAV/VNAV final.
(35) Paragraph 2-11-5.b(3)(a) Note. Added 15 minute quadrangle series as permissible.
(36) Paragraph 2-11-5.c. Added reference to Order 8260.58, chapter 4 for LNAV/VNAV final.
(37) Paragraph 2-11-5.c(3)(c). Changed “OIS” to “obstacle clearance surface (OCS)” to match Order 8260.3 usage.
(38) Paragraph 2-11-5.c(3)(c). Added reference to 40:1 OCS.
(39) Paragraph 2-11-4. Editorial changes and added references.
(40) Paragraph 2-12-2d. Removed paragraph regarding use of collision risk model (CRM).
e. Chapter 3.
(1) Paragraph 3-1-1.b. Updated reference to proper criteria used for development of Q and T routes.
g. Chapter 5. › (2) Paragraph 5-2-4.k(3). Editorial to match what is in paragraph…
(2) Paragraph 3-5-1.a. Updated process to bring in line with current practices, to include RAPT involvement.
(3) Paragraph 3-7-4.b. Added “The FAA will…” to indicate whom this pertain to.
f. Chapter 4.
(1) Paragraph 4-1-3.d. Updated Order 8260.26 subject title.
(2) Paragraph 4-1-5. A number of sub-paragraphs deleted that contained guidance that has been incorporated into Order 8260.3C. Paragraph numbering/lettering revised accordingly.
(3) Paragraph 4-1-6.i. Clarified guidance for calculating sidestep visibility minimums.
(4) Paragraph 4-1-6.i(6). Added to provide guidance on additional steps needed when credit is taken for full approach light system (FALS).
(5) Removed section 4-3, Direction Finder (DF) Procedures. All chapter 4 sections and paragraphs have been re-numbered accordingly.
(6) Section 4-5. Completely revised to support Flight Standards (AFS-420) assuming responsibility of the policies specified in Order JO 7100.9, Standard Terminal Arrival Program and Procedures.
(7) Paragraph 4-6-2.e Note. Clarified that instrument approaches can be developed using RNAV criteria for Initial, Intermediate and Missed Approach segments of ILS/LOC procedures.
(8) Paragraph 4-6-5.j. Added paragraph to describe RNAV FM leg type.
(9) Paragraph 4-6-8. Moved portion of guidance to notes portion of chapter 8; new paragraph 8-6-6.t.
(10) Paragraph 4-6-9. Revised paragraph based on AFS-470 input driven by a change to Flight Inspection policy. Added (AFS-450 input) tolerance for situations when revised/updated coordinates have been inserted into the AIRNAV database.
(11) Paragraph 4-6-10.j. Removed reference to “RNP” to allow for guidance to apply to all RNAV approach types, when needed. Added guidance to specify speed restrictions associated with the missed approach procedure to appear at the beginning of the missed approach instructions.
(12) Paragraph 4-6-10.k. Changed reference from “RNP” to read “RNAV” and added guidance to address situations where there are multiple intermediate segments.
g. Chapter 5.
(1) Paragraph 5-2-4.c(1)(b). Editorial – Added “…to terrain as described in…”
(2) Paragraph 5-2-4.k(3). Editorial to match what is in paragraph 5-2-4.k(6).
h. Chapter 8.
(1) Paragraph 8-2-1.b(1). Added GLS.
(2) Paragraph 8-2-1.d. Editorial; removed unnecessary text.
(3) Paragraph 8-2-2.b. Revised procedures aligned to specific 14 CFR part 97 subparts due to a revision in procedure naming as published in change 26 to Order 8260.3B, Volume 1, section 6.
h. Chapter 8. › (17) Paragraph 8-5-2.g(1). Provided examples for multiple fix types.
(4) Paragraph 8-2-2.c. Editorial and added sentence for clarity regarding combining RNAV approach procedures.
(5) Paragraph 8-2-5.e. Editorial; changed “required” to “established.” Added guidance to restrict use of feeder routes where a turn from an airway on to the feeder route exceeds the limitations specified in Orders 8260.3 and 8260.58 [see Aeronautical Charting Forum, Instrument Procedures Group agenda item 07-01-270].
(6) Paragraph 8-3-2.a. Changed to leave box blank; requirement for accomplishing and documenting periodic reviews are specified in paragraph 2-8-1.
(7) Paragraph 8-3-2.c(3). Added runway construction projects for Hard Date application.
(8) Paragraph 8-3-2.d Note. Last sentence; changed responsibility from AFS-460 to RAPT for resolving valid user comments that cannot be resolved by Aeronautical Information Services.
(9) Paragraph 8-3-4.a(8). Added “Note” to clarify an exception that this paragraph does not apply when runway is extended or when the threshold is displaced.
(10) Paragraph 8-3-4.b(10). Added “runway threshold/end location” to this limitation.
(11) Paragraph 8-3-4.b(21). Added guidance to include chart note that permits lowering RVR in support of operational capabilities.
(12) Paragraph 8-3-4.c. Added Flight Inspection order reference and revised portion to clarify exception limits where changes to minima are involved.
(13) Paragraph 8-3-4.c(3). Sentence deleted. Paragraph numbers revised accordingly.
(14) Paragraph 8-4-1.i(1). Deleted last sentence at the request of AFS-460.
(15) Section 8-4, figure 8-4-1 updated with current form.
(16) Paragraph 8-5-2.g(1)example. Removed fix examples that implied holding could be established over an Outer Marker or Fan Marker.
(17) Paragraph 8-5-2.g(1). Provided examples for multiple fix types.
h. Chapter 8. › (33) Paragraph 8-6-5.m(1). Editorial – Changed “operation” to…
(18) Paragraph 8-5-2.g(3). Editorial changes; NAVAID references.
(19) Paragraph 8-5-2.g(5). Revised to indicate that a Special procedure reference in the “Fix Restriction” entry is only required when the fix is used for a Special procedure (i.e., is not used on a public, 14 CFR part 97 procedure).
(20) Paragraph 8-6-2.a(6)(a). Added paragraph to document “(FAF)” after PFAF name; following sub-paragraph up-lettered.
(21) Paragraph 8-6-3.d. Editorial changes to segregate ILS and RNAV applications.
(22) Paragraph 8-6-3.f(1). Text: “…rounded to the next higher 100-foot increment” removed; applicable intercept altitude is controlled by criteria specified in Order 8260.3 and Order 8260.58.
(23) Paragraph 8-6-3.g(1) Note. Added note to clarify when “GS” and “GP” will be used when describing the angle of a vertically guided approach.
(24) Paragraph 8-6-3.h(1). Editorial and added guidance to support new Order 8260.3 criteria that permits use of an airport reference point (ARP) as a MSA center.
(25) Paragraph 8-6-5.c. Revised text to indicate when a Procedure Turn is less than 10 NM, it is limited to CAT A only.
(26) Paragraph 8-6-5.f. Removed “military” from sentence because a request for category (CAT) E minimums could now come from other sources.
(27) Paragraph 8-6-5.g(1) & 8-6-5.g(2). Expanded guidance relating to non-RNAV procedure documentation and added guidance for properly annotating ILS and LOC helicopter procedures to a runway.
(28) Paragraph 8-6-5.g(3). First sentence; changed “establish” to read “document.”
(29) Paragraph 8-6-5.i(3). Added runway number to sample chart note to indicate the restriction only applies to the runway with the 20:1/34:1 surface penetration.
(30) Paragraph 8-6-5.k. Added a paragraph “(7)” regarding a chart note needed for conditions that do not allow for the localizer to be used for rollout guidance.
(31) Paragraph 8-6-5.l(1). Editorial; added “source” for clarity.
(32) Paragraph 8-6-5.l(3)(c). Editorial to support changes to procedure naming (change 26 to Order 8260.3B, Volume 1, section 6).
(33) Paragraph 8-6-5.m(1). Editorial – Changed “operation” to “availability” and “authorizing” to “permitting.”
(34) Paragraph 8-6-5.m(2)(g) and 8-6-5.m(2)(h). Revised guidance on applicable chart note for straight-in/circling limitations when there are obstacles impacting the visual portion of final [see US-IFPP agenda item 15-01-26 and ACF-IPG agenda item 09-02-291].
h. Chapter 8. › (47) Paragraph 8-6-6.q(2). Added statement to not include LOC minimums…
(35) Paragraph 8-6-5.m(3)(a), 8-6-5.m(3)(d), 8-6-5.m(3)(e), and 8-6-5.m(3)(f). Changed from stating the specific lighting system to generically stating “ALS” for approach light system.
(36) Paragraph 8-6-5m(6). Added sub-paragraph “(f)” guidance regarding “RA NA” as an additional ILS restriction.
(37) Paragraph 8-6-5m(7) and subparagraph (a). Revised guidance to shorten the chart note used to support simultaneous operations.
(38) Paragraph 8-6-5m(7)(b). Added guidance for situations where there are 3 or more parallel runways and Order JO 7110.308 does not apply to all of them.
(39) Paragraph 8-6-5.m(7)(d). Removed reference to “RNAV (RNP)” since the requirement for use of Flight Director or Autopilot is part of the certification/approval process. Added guidance stating that this chart note may also be necessary for ILS procedures under certain ATC operations as defined in applicable TERPS and ATC directives.
(40) Paragraph 8-6-5.m(8). Added paragraph providing guidance for chart note requirement for converging approach operations. Following paragraphs re-numbered accordingly.
(41) Paragraphs 8-6-6.e(8). Added “precipitous terrain” to the “Baro-VNAV NA” limitation.
(42) Paragraph 8-6-6.g(2). Added RNAV 1 to be consistent with changes made in paragraph 8-6-6.h(4) and 8-6-6.h(5).
(43) Paragraphs 8-6-6.h(2). Editorial change to add clarity.
(44) Paragraphs 8-6-6.h(4) and 8-6-6.h(5). Added provision to, where permitted, also allow for DME/DME/IRU use for RNAV segments on ILS or LOC instrument procedures. Added note to clarify that a briefing strip note requiring RNAV is not required when ILS or LOC procedures can be flown from the IF to missed approach clearance limit without RNAV.
(45) Paragraph 8-6-6.q. Broke paragraph into three sub-paragraphs. Revised paragraph to reduce chart note text required when describing simultaneous approach authorization.
(46) Paragraph 8-6-6.q(1). Added reference to having an Attention All Users Page (AAUP) with section reference and added clarification to the chart note to show that the requirement only applies to ILS procedures.
(47) Paragraph 8-6-6.q(2). Added statement to not include LOC minimums on ILS PRM procedures.
h. Chapter 8. › (65) Paragraph 8-6-9.c. Added guidance for GLS procedures.
(48) Paragraph 8-6-6.q(3). Added statement to not include LP or LNAV minimums on RNAV (GPS) PRM procedures.
(49) Paragraph 8-6-6.r. Added “RNAV (GPS) RWY 28R” to examples. Revised paragraph to reduce chart note text required when describing simultaneous approach authorization.
(50) Paragraph 8-6-6.r(2). Added “Radar” to the chart note requirement per AFS-450 study showing this requirement for SOIA operations.
(51) Paragraph 8-6-6.r(3). Added guidance unique to SOIA aircraft database coding requirements.
(52) Paragraph 8-6-6.r(4). Added guidance regarding a chart note that may be necessary when the offset procedure has been evaluated for a go-around after leaving the DA and a greater than 200 ft per NM climb gradient is required.
(53) Paragraph 8-6-6.t. New paragraph with updated guidance from paragraph 4-6-8.
(54) Paragraph 8-6-7.c. Editorial changes made for clarity.
(55) Paragraph 8-6-7.d. Editorial changes which resulted in re-numbering sub-paragraphs.
(56) Paragraph 8-6-7.d(1). Added guidance and example of RNAV speed restrictions at the beginning of the missed approach instructions.
(57) Paragraph 8-6-7.e(1). Revised guidance to move missed approach climb gradient information from the notes box in the briefing strip of the approach chart, to immediately following the missed approach instructions.
(58) Paragraph 8-6-7.e(3). Editorial change made for clarity.
(59) Paragraph 8-6-7.f. Deleted redundant sentence.
(60) Paragraph 8-6-8.k(6). Added guidance for GBAS procedures.
(61) Paragraph 8-6-8.r. Added intermediate segment as requiring Flight Standards approval when maximum, mandatory, or block altitudes will be used.
(62) Paragraph 8-6-8.s. Added guidance to require a chart note for when Flight Inspection has denied VDA publication.
(63) Paragraph 8-6-8.v. Removed “Ceiling requirements” paragraph; requirement removed from Order 8260.3.
(64) Paragraph 8-6-8.y. Added guidance to document “OTA Procedure” when a 14 CFR part 97 procedure is developed under an OTA.
(65) Paragraph 8-6-9.c. Added guidance for GLS procedures.
h. Chapter 8. › (83) Section 8-11.
(66) Paragraph 8-6-9.d(1). Deleted paragraph due to changes in procedure naming (change 26 to Order 8260.3B, Volume 1, section 6). Paragraphs re-numbered accordingly.
(67) Paragraph 8-6-9.d(3). Removed “Simultaneous” from the text in parenthesis below the PRM procedure name and now reads only “Close Parallel.”
(68) Paragraph 8-7-1.b(6). Revised last sentence to account for a different HMAS for LNAV/VNAV procedures.
(69) Paragraph 8-7-1.b(12). Refining ROC guidance for LNAV/VNAV procedures.
(70) Paragraph 8-7-1.b(20). Removed requirement to attach a copy of VEB spreadsheet.
(71) Paragraph 8-7-1.b(24). Added airport reference point (ARP) option in support of Order 8260.3 change to permit this option when necessary.
(72) Paragraph 8-7-1.c(10). Revised and expanded guidance based on input received from Aeronautical Information Services, AJV-5.
(73) Paragraph 8-7-1.c(11). Removed reference to accuracy values for RNP procedures and added documentation to include circling at the request of Aeronautical Information Services.
(74) Paragraph 8-8-2.b. Editorial and noted that radar missed approach instructions will not be charted.
(75) Paragraph 8-8-2.d. Added guidance to ensure only those notes specifying “Chart Note” will be charted.
(76) Paragraph 8-8-3.b(2). Editorial changes made to clearly state when an ODP would be required where Special instrument procedures are being developed.
(77) Paragraph 8-8-3.c. Changed last sentence to show that AFS-410/470 not only develops what goes on Form 8260-7B, but also approves the guidance specified on the form.
(78) Section 8-10. Changed title and Form 8260-16 name to “Transmittal of Airways/Route Data Record” and all samples for Form 8260-16 were updated using Adobe LiveCycle Designer.
(79) Paragraph 8-10-1. Added reference to TK Route.
(80) Paragraph 8-10-1.a. Added example for TK Route.
(81) Paragraph 8-10-1.f(1). Added reference to TK Route.
(82) Paragraph 8-10-1.o. Rewrote last sentence at the request of Aeronautical Information Services to exclude a “line through” capability due to this being impossible with the processing of electronic FAA Forms.
(83) Section 8-11. Added to incorporate guidance for establishing/developing an AAUP.
i. Appendix A.
(1) Paragraph 2c. Added “…and/or maintains…”
(2) Table 1. Updated acronyms and abbreviations.
(3) Table 2. Updated forms, removing U.S. Army and U.S. Air Force Forms.
j. Appendix B.
Section 1-1. General › 1-1-6. Effective Date.
(1) Table 1. Updated orders.
(2) Table 2. Updated new number for Instrument Procedures Handbook and Advisory Circulars.
k. Appendix D. Added statement in block 6 that added a requirement to specify whether values are magnetic or true and provide the magnetic variation used for the computations.
l. Appendix L.
(1) Opening statement. Editorial changes.
(2) Paragraph 4d. Added a note regarding helicopter procedures.
(3) Paragraph 4i. Expanded guidance to address truncating values and the range of values that can be used.
(4) Paragraph 4o. Deleted reference.
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 (AFS400). › Flight Operations Branch (AFS410).
Section 1-2. Responsibilities
Note: Applicable FAA 1100-series orders 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 (AFS-1).
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 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 (AFS-400). 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 (AFS-400).
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 under 14 CFR part 97. The division is also responsible for approval/disapproval of special instrument approach procedures and approval for waivers of standards.
b. Flight Operations Branch (AFS-410). AFS-410 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. It 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. 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). 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
1-2-2. Flight Technologies and Procedures Division (AFS400). › f. Flight Procedure Implementation and Oversight Branch (AFS-460).…
original equipment manufacturers (OEMs), Aircraft Certification (AIR), and Aircraft Evaluation Groups (AEGs), identifies explicit operational credit for pilots using new-technology products. Provides specific Operations Specification (OpsSpec) language and inspector guidance regarding low visibility operations (CAT II/III) procedures and minima.
c. Flight Procedure Standards Branch (AFS-420). AFS-420 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 (AFS-460), 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 (AFS-440). AFS-440 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 AFS offices, ATO, airports, regions, 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 (AFS-450). AFS-450 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 AFS offices, ATO, airports, regions, 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 (AFS-460). AFS-460 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
b. The RNGB responsibilities include but are not limited to the… › (2) Providing technical evaluations in support of regional airspace…
evaluations, and monitoring validation flights. AFS-460 develops policy for flight validation of IFPs and manages the program for the review and approval of all Special IFP and waivers to design criteria and standards. AFS-460 is responsible for coordinating non-government procedure developer NOTAM authority and access to the NOTAM Entry System (NES) with ATO Mission Support Services, Aeronautical Information Management (AIM) Office. 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. AFS-460 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 (AFS-470). AFS-470 is the principal element within the division, with respect to performance based navigation across all domains. 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. 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. Provides guidance to develop OpsSpec requirements (including parts C and H) related performance based navigation, operating minimums, equipment, and training. 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.
1-2-3. Regional Flight Standards Divisions (AXX-200).
a. Regional Flight Standards Divisions (RFSD). The RFSD manages and directs the geographic regions’ air carrier, general aviation, and all weather operations programs. Each RFSD provides the regional implementation of national concepts, policies, standards, systems, procedures, and programs with respect to the operational and flight technical aspects of the allweather operations program. The RFSDs’ NextGen Branches (RNGB) are assigned specific task processes and derive their guidance for determining appropriate signature level and task responsibilities as specified by their Job Task Analysis.
b. The RNGB responsibilities include but are not limited to the following:
(1) Establishing regional requirements for and managing distribution of, special instrument approach procedures. Receiving and resolving user/industry comments on new and revised special instrument approach procedures. Supporting national programs under the direction of AFS-400 such as the Required Navigation Performance/Authorization Required (RNP/AR) instrument approach procedure (IAP) program.
(2) Providing technical evaluations in support of regional airspace programs to determine the effect on operational safety and visual flight operations. Specific study responsibilities for RFSDs 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
1-2-4. › a. AJW-3 is the principal element within the Technical Operations…
operations utilizing RNGB missed approach tool, assessing operational safety for taxiway/runway separation, and configuration relative to a proposed CAT II/III, etc.).
(3) Coordinating the RNGB portion of assigned foreign instrument approach procedures programs as specified in Order 8260.31, Foreign Terminal Instrument Procedures (FTIPs).
(4) Approving for the RFSD each CAT II and III operation and coordinating continuity of service assurance with the ATO Service Area. Related to CAT III approvals is the RFSD 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.
(5) Providing the operational input on matters related to regional capacity studies and airport operational safety initiatives.
(6) 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.
(7) Providing the consolidated RFSD position for review of charted visual flight procedures and RNAV visual flight procedures.
(8) 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].
(9) 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.
(10) When requested by the Flight Procedures Field Office (FPFO), assists in developing the equivalent level of safety for an Aeronautical Information Services (AIS) originated procedures waiver.
(11) In coordination with AFS-460, participates in and provides region level support when requested for activities related to non-FAA service providers.
1-2-4. Air Traffic Organization, Technical Operations Flight Inspection Services (AJW-3).
a. AJW-3 is the principal element within the Technical Operations Services (AJW-0) 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 ARINC code which represents the IFP in the Flight Management System (FMS). Flight Inspection Services provides flight inspection for the Department of Defense (DoD) on foreign navigational
1-2-5. Air Traffic Organization, Mission Support Services (AJV-0). › a. Aeronautical Information Services (AJV-5) is directly responsible…
facilities that have been designated as essential to the defense of the United States. Flight Inspection Services is also responsible for input 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 Services Group (FPSG) is the principal element within AJW-3 responsible for scheduling flight inspections. FPSG maintains liaison with AIS, as well as other FAA offices, civil and military interests, to ensure consideration of all requirements relating to the procedural use of navigation facilities. FPSG’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.
(10) Maintaining a National Liaison Office located at the Air Traffic Control System Command Center (ATCSCC) to ensure responsive restoration and maintenance of critical NAS services.
c. Flight Inspection Operations Group (FIOG) is the principal element within AJW-3 responsible for flight inspection of navigation aids and instrument flight procedures in support of the NAS. The FIOG operates six geographically separated field offices.
1-2-5. 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
(2) The Geographic Services Group is the principal element within AJV-5… › (b) Collecting, validating, managing, and disseminating as-built…
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 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) The Geographic Services Group is the principal element within AJV-5 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. Geographic Services is 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 AIS through the ICAO.
(b) Collecting, validating, managing, and disseminating as-built obstacle data reported under 14 CFR part 77.
b. Aeronautical Information Services (AJV-5) is also responsible for… › (12) Establishing procedures to ensure operational data are included in…
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.
(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 (AIS).
(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 AIS.
(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.
Section 1-2. Responsibilities › 1-2-6. Individual.
(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. Service Area, 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.
(10) Acting as the focal point for flight inspection issues within the region.
1-2-6. 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.
a. Responsible for administrative control of instrument procedure… › (4) Determining that all proposed changes are essential to the…
Section 1-3. Instrument Procedure Development Software Responsibilities
Note: Organizational responsibilities and functions are addressed in applicable 1100-series orders. 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. This section must not be interpreted as a substitute or supplement to any other FAA directive. 1-3-1. Background.
a. The FAA has developed software to implement the Instrument Flight Procedures Program to include the development, review, storage, and electronic transmittal of instrument flight procedures with ancillary system benefits.
b. The FAA instrument procedure software applies criteria specified in Order 8260.3, United States Standard for Terminal Instrument Procedures (TERPS), Order 8260.19, and other appropriate directives, advisory circulars, software specifications, and CFRs.
1-3-2. Flight Procedure Standards Branch’s responsibility. AFS-420 is the office of primary interest and is responsible for software requirements related to administration of the National Flight Procedures Program and for implementation of criteria pertinent to the design of instrument flight procedures.
1-3-3. Aeronautical Information Services (AJV-5) responsibility. This is the office of primary interest that is responsible for overall functional management of the FAA instrument procedures software/databases and for ensuring the implementation of AFS-420 defined software requirements.
a. Responsible for administrative control of instrument procedure software, as well as coordinating actions required to meet changing legal and user requirements. In addition, this group is responsible for:
(1) Carrying out the development of instrument procedure software by coordinating the efforts of users, developers, operators, and contractors associated with instrument procedure software.
(2) Managing and reporting on project schedules, costs, and other supporting resources for the Air Traffic Technical Operations Service Information Resource Manager.
(3) Establishing and maintaining a positive change control management system through the developmental and implementation phases to assure that the completed project (the operational instrument procedure software) meets the requirements of the system definition.
(4) Determining that all proposed changes are essential to the development task and are coordinated among all prospective users of the system.
Section 1-3. Instrument Procedure Development Software Responsibilities › 1-3-4. Information Technology Shared Service Organization (AIT).
(5) Keeping contracting officers advised, if appropriate, on proposed changes in order that the officer may be alerted to the impact that they may have on current or proposed contractual actions.
(6) Preparing for and participating in validation tests and evaluations of the information system.
(7) Assuring system software is in conformance with established software requirements.
b. Production Technology and ATC Products Group (AJV-36). The Production Technology and ATC Products Group is responsible for assuring the successful ongoing operation of the data system. In the performance of these responsibilities, the team must:
(1) Establish and maintain a positive change control management system to assure that all changes to the operational instrument procedure software system are cost effective and are coordinated among all parties who use the FAA instrument procedure software.
(2) Develop necessary guidelines for the control and dissemination of data from the FAA instrument procedure software and other assigned systems.
(3) Authorize release of data in special cases where guidelines are not available.
(4) Provide for coordination in data systems where several program elements share primary operational interest.
(5) Establish priorities for task assignments, scheduling, and utilization of personnel and physical resources.
(6) Assure system configuration, documentation, and reliability.
(7) Conduct extensive operational testing and debugging, to assure system software is in conformance with Order 8260.3 and other appropriate directives, advisory circulars, and 14 CFR provisions. Conduct final system certification of software before release to users through coordination with AFS-420.
(8) Review national user requirements and approve system modifications.
(9) Ensure that the provisions of Order 1370.82, Information Systems Security Program, are compiled within the security control of computer programs and associated documentation.
1-3-4. Information Technology Shared Service Organization (AIT). The Information Technology Shared Service Organization is responsible for establishing and maintaining the FAA Enterprise Data Architecture. The FAA Enterprise Data Architecture is the Authoritative Source for recording approved designated data sources, responsible stewardship (stewards, custodians, etc.), and any required data precision/resolution. Standards for data precision/resolution required for the development, storage, and electronic transmittal of instrument flight procedures are specified in the FAA Enterprise Data Architecture website.
Section 1-3. Instrument Procedure Development Software Responsibilities › 1-3-7. Vice President for Mission Support Services (AJV-0).
1-3-5. Office of Information Services (AMI-1). The Office of Information Services is responsible for the software development from its inception through implementation. This office is also responsible for maintenance of system software, and must provide and control automatic data processing (ADP) resources that include:
a. Utilizing personnel (including contract personnel) and physical resources.
b. Providing technical consultation and advice as required.
c. Providing telecommunications support, and other necessary ADP enhancement and support services for instrument procedure software.
d. Participating in the review of site preparation, installation, and testing support as required.
e. Providing on-site hardware and software installation and testing support as required.
f. Providing preliminary testing of software to assure conformance with established software requirements.
1-3-6. Office of Assistant Administrator for Information Services (AIO-1). The Office of Assistant Administrator for Information Services will develop governing policies and responsibilities for ADP program management in accordance with Order 1370.52, Information Resources Policy.
1-3-7. Vice President for Mission Support Services (AJV-0). The Vice President for Mission Support Services is responsible for the determination of agency-wide priorities for use and control of telecommunications resources needed to support FAA instrument procedure software. This responsibility is administered through the Telecommunications Integrated Product Team in the NAS Operations Program (AOP) of the Air Traffic Organization, Technical Operations.
a. Operation of airport lighting and visual aids is contained in the… › (2) Order JO 7110.65, Air Traffic Control.
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 AFS personnel. General information on the lifecycle process associated with IFPs can be found in appendix O.
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 AIS. All other projects will be processed as workload permits, by AIS in order of receipt.
2-1-2. Air Traffic Letters of Agreement (LOAs). When letters of agreement affect or include flight procedures, they must be coordinated between ATC facilities and AIS.
a. When these letters are received, AIS must review them to ensure compatibility with published or planned flight procedures.
b. Copies of letters of agreement received in AIS must be made a part of the procedure files, to serve as a reference when developing or amending flight procedures.
c. When the terms of the letters of agreement and flight procedures are not compatible, or if it is determined that the terms do not comply with criteria, AIS must return the letters 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, a letter of agreement is an agreement between two or more ATC facilities. Unless AIS 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) 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.
2-1-3. Airport lighting and visual aids. › c. Refer to appendix B, Flight Procedures References, for other…
c. Refer to appendix B, Flight Procedures References, for other applicable orders and advisory circulars.
Section 2-2. Aeronautical Charts
2-2-1. Use of maps and charts.
a. AIS 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, AIS 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.
2-2-2. Aeronautical charts and publications. › d. AIS is responsible for the accuracy and completeness of flight data…
b. Map requirements for inclusion in a flight inspection package are determined by the Flight Inspection Technical Services Team [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). AFS-400 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 Production Technology & ATC Products Group (AJV-36).
c. AIS 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. AIS 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. AIS 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 discrepancies and/or…
e. AIS 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 discrepancies and/or errors in aeronautical charts and/or AIM and AIP discrepancies should be referred to Air Traffic and Terminal Products (AJV-5600).
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 RFSD and the OSG-FPT. The RFSD 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
2-4-3. Requests for Expanded Service Volumes. › c. The procedures specialist when developing an instrument procedure…
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 above/beyond limitations cited in paragraphs 2-4- 3.a through 2-4-3.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 AIS.
b. AIS 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 AIS 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.
b. Monitoring categories. Navigational facilities are classified in… › (4) Category 4.
d. Facility rotation due to magnetic variation change should have no effect on coverage; however, radials used will change. AIS initiates a change action via the spectrum management web site (ESVMS) on the date the rotation is effective.
e. For holding patterns, process an ESV request for the holding fix. Describe holding fix by radial, distance, altitude.
f. An ESV is prepared and processed electronically via the ESVMS via the FAA Intranet web site. An ESV can be placed on any very high frequency omnidirectional range (VOR), instrument landing system–distant measuring equipment (ILS-DME), or tactical air navigation (TACAN). When a DME or TACAN and VOR are paired, both must have identical ESVs for safety reasons (except in those cases where the DME ESV supports DME/DME area navigation (RNAV) operations). ESVs may be added to any class of NAVAID facilities, including NDBs.
2-4-4. Utilization of localizers as en route aids. The use of a localizer in en route flight procedures may be authorized in accordance with the following limitations:
a. The use of the localizer for lateral course guidance is not authorized.
b. A localizer may serve as a crossing facility where it is essential to air traffic control.
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-4.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-1d.
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. AIS. › (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) AIS.
(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. AIS.
(1) Publish isogonic lines or segments on appropriate aeronautical charts based on current epoch year values.
a. AIS. › (10) Amend instrument flight procedures as required, predicated on…
(2) Revise en route aeronautical charts and Airport/Facility Directives (AFDs) to reflect revised MV assignments to navigation facilities in accordance with information published in the NFDD.
(3) Revise en route charts to apply yearly MV change values to RNAV (“Q” and “T”) route Magnetic Reference Bearings (MRB) during the first airspace charting cycle of each calendar year.
(4) Function as the focal point for all information relating to application of MV to the following elements of the NAS: NAVAIDs, airports, instrument flight procedures; and for coordination and liaison between AIS and the applicable Air Traffic Service Area 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-8.n and 8-6-8.o].
(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 AIS 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 AIS 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-8.n and 8-6-8.o].
d. OSG-FPT. › (2) The OSG-FPTs will coordinate with the regional airports and Air…
(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 AIS 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 AIS 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 AIS’ flight procedure development work as outlined in paragraphs 2-5-2.b(3) through 2-5-2.b(9). AIS 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 AIS of changes to U.S. Navy, non-NAS facilities, assigned MV and the effective date of those changes in order to allow AIS 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.
(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 AIS when MV changes are required. Allow sufficient time for modification of FAA fixes and IAPs as necessary. National Flight Data Center, when notified by AIS 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 AIS of MV changes when informed by non-FAA service providers maintaining instrument procedure(s) they are responsible for.
(2) The OSG-FPTs will coordinate with the regional airports and Air Traffic offices with respect to matters pertaining to change in navigational aid or airport MV of record and its effect on instrument flight procedures.
2-5-3. Guidelines for Magnetic Variation (MV) revisions. › c. MV limits for airports with SA CAT II or CAT II/III approach…
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 AIS, 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 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 degrees, 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 degrees (3.0). Off-airport NAVAIDs must be maintained within three degrees (3.0), 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
(2) RNAV. › (a) Instrument approach procedures (IAPs)/DPs/STARs, including GLS.
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 all 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 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 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 ARINC 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.
Continue reading ↓ 120 of 962 passages shown