Radar Vectors
FAA Order Cancelled Issued Jan 9, 2014 AFS-400 456 pages Copy saved Nov 18, 2026

Order 8260.19F Flight Procedures and Airspace

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

Official source ↗ Open PDF

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

U.S. DEPARTMENT OF TRANSPORTATION ORDER FEDERAL AVIATION ADMINISTRATION 8260.19F

U.S. DEPARTMENT OF TRANSPORTATION ORDER FEDERAL AVIATION ADMINISTRATION 8260.19F

Effective Date: National Policy 01/09/14

SUBJ: Flight Procedures and Airspace

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

2. 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 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 (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.

3. Guidelines and procedures mat are common to all instrument flight procedures are in chapter 1, Chapters 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 Barbagallo Deputy Director, Flight Standards Service

Distribution: Electronic Distribution Initiated By: AFS-400

01/09/2014 8260.19F

Table of Contents

Chapter 1. General Information 11

Chapter 1. General Information 11

Section 1-1. General

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

Section 1-2. Responsibilities 19 1-2-1. Flight Standards Service (AFS-1) 19 1-2-2. Flight Technologies and Procedures Division (AFS-400) 19 1-2-3. Regional Flight Standards Divisions (AXX-200) 21 1-2-4. Technical Operations Flight Inspection Services (AJW-3) 22 1-2-5. Air Traffic Organization, Mission Support Services (AJV-0) 23 1-2-6. Individual 26 1-2-7. Transferring Instrument Procedure Maintenance Responsibilities 26

Section 1-1. General

Section 1-3. Instrument Procedure Development Software Responsibilities 27 1-3-1. Background 27 1-3-2. Flight Procedure Standards Branch's Responsibility 27 1-3-3. Aeronautical Navigation (AeroNav) Products (AJV-3) Responsibility 27 1-3-4. Information Technology Shared Service Organization (AIT) , 29 1-3-5. Office of Information Services (AMI-1) 29 1-3-6. Office of Assistant Administrator for Information Services (AIO-1) 29 1-3-7. Vice President for Mission Support Services (AJV-0) 29

Chapter 2. General Procedures 31

Chapter 2. General Procedures 31

Section 2-1. General 31 2-1-1. Requests for Public-Use Instrument Flight Procedures (IFPs) 31 2-1-2. Air Traffic Letters of Agreement 31 2-1-3. Airport Lighting and Visual Aids 31

Section 2-2. Aeronautical Charts 33 2-2-1. Use of Maps and Charts 33 2-2-2. Aeronautical Charts and Publications 33

Section 2-3. Environmental Requirements 35 2-3-1. Noise Abatement 35 2-3-2. Environmental Impacts 35

Section 2-4. Facility Utilization and Monitoring 36 2-4-1. Frequency Service Volumes 36 2-4-2. ATC Usable Distance and Altitude Limitations 36 2-4-3. Requests for Expanded Service Volumes (ESV) 38 2-4-4. Utilization of Localizers as En Route Aids 39

01/09/2014 8260.19F

2-4-5. Monitoring of Navigation Facilities 39 2-4-6. Utilization of Monitoring Categories 40 2-4-7. Utilization of 75 MHz Markers 40

Section 2-5. Implementing Epoch Year Magnetic Variation (MY) 42 2-5-1. General Values 42 2-5-2. Responsibilities 42 2-5-3. Guidelines 47

Section 2-6. Notices to Airmen (NOTAMs) 50 2-6-1. General 50 2-6-2. United States NOTAM System 50 2-6-3. Instrument Flight Procedure NOTAMs 50 2-6-4. FDC NOTAM Preparation, Review, and Transmittal Responsibilities 52 2-6-5. Instrument Flight Procedure NOTAMs 55 2-6-6. Chart Correction NOTAMs 56 2-6-7. General NOTAM D Actions 56 2-6-8. Air Traffic Service Route NOTAMs 59 2-6-9. FDC NOTAMs for Special Instrument Approach Procedures (Specials) 60 2-6-10. NOTAM Content 61

Section 2-7. Quality/Standardization ofInstrument Flight Procedures 64 2-7-1. AeroNav Products Action 64 2-7-2. AFS-460 Action 64

Section 2-8. Periodic Review of Instrument Flight Procedures 65 2-8-1. General 65 2-8-2. Reviewing Organization Action 66

Section 2-9. Communications and Weather 68 2-9-1. Communications Requirements 68 2-9-2. Use of UNICOM 68 2-9-3. Automatic Altimeter Setting and Weather Reporting Systems 68 Section 2-10. Navigational Fixes 70 2-104. General 70 2-10-2. Reporting Points 70 2-10-3. Unplanned Holding at Designated Reporting Points 70 2-10-4. Requests for Navigational Fixes 70 2-10-5. Naming Navigational Fixes 71 2-10-6. Documenting Navigational Fixes 73 2-10-7. Correlation of Navigational Fixes and Changeover Points (COPs) 73 2-10-8. Minimum Reception Altitudes 74 2-10-9. Flight Inspection 74 2-10-10. Maximum Authorized Altitudes 75

Section 2-11. Obstacle Data 76 2-11-1. General 76 2-11-2. Obstacle Data Sources 76 2-11-3. Obstacle Data Accuracy Standards 76

01/09/2014 8260.19F

2-11-4. Accuracy Standards Application 78 2-11-5. Controlling Obstacles 78 2-11-6. Datums 83

Section 2-12. Waiver of Standards/Approval Requests 85 2-12-1. General 85 2-12-2. Waiver Processing 85 2-12-3. Waivers for Special Instrument Approach Procedures 86 2-12-4. Safety Management System (SMS) Requirements 86 2-12-5. Periodic Review of Waivers 87 2-12-6. Cancellation of Waivers 87

Chapter 3. En Route Procedures 89

Chapter 3. En Route Procedures 89

Section 3-1. General 89 3-1-1. General 89 3-1-2. Publication 89

Section 3-2. Criteria Application and Development 90 3-2-1. Criteria Application 90 3-2-2. Development of Criteria 90

Section 3-3. Establishment of En Route Airspace 91 3-3-1. Relationship of COPs to Air-Space Dimensions 91 3-3-2. Relationship of MEAs to Controlled Airspace Floors 91

Section 3-1. General 89 3-1-1. General 89 3-1-2. Publication 89

Section 3-4. Substitute En Route Flight Procedures 92 3-4-1 General 92 3-4-2 Format 92 3-4-3 Facilities Used 92 3-4-4 Controlled Airspace 92 3-4-5 Flight Inspection 92 3-4-6 Planning and Coordination 93 3-4-7 Processing 96 3-4-8 Periodic Review 96 3-4-9 Distribution 96

Section 3-5. Off-Airway Routes 98 3-5-1. Establishment 98 3-5-2. Listing 98 3-5-3. Off-Airway Data 98 3-5-4. Processing Data to NFDC 98

Section 3-6. New or Revised National Airspace System Routes 99 3-6-1. Definition - Route 99 3-6-2. Coordination Procedures 99 3-6-3. Publication of Procedural Data 99

Section 3-7. Minimum Vectoring Altitude (MVA) and Minimum IFR Altitude (MIA) Charts. 100

Section 3-7. Minimum Vectoring Altitude (MVA) and Minimum IFR Altitude (MIA) Charts. 100

3-7-1. Chart Preparation 100 3-7-2. Obstacle Clearance 100

01/09/2014 8260.19F

3-7-3. Controlled Airspace 100 3-7-4. Chart Review and Approval 100 3-7-5. Emergency Obstruction Video Map (EOVM) 101

Chapter 4. Terminal Procedures , ...103

Chapter 4. Terminal Procedures , ...103

Section 4-1. General 103 4-1-1. General 103 4-1-2. Categories of Instrument Approach Procedures 103 4-1-3. Airspace Requirements 103 4-1-4. Contractual Use of Private Facilities 104 4-1-5. TERPS Application 104 4-1-6. Sidestep Maneuvers 109 4-1-7. Temporary Displaced Threshold Procedures 110

Section 4-2. Standard Instrument Approach Procedures (SIAP) 112 4-2-1. General 112 4-2-2. Coordination of Terminal Instrument Procedures 112 4-2-3. Radar Instrument Approach Procedures 112

Section 4-3. Direction Finder (DF) Procedures 113 4-3-1. General 113 4-3-2. Format 113 4-3-3. Application of Criteria 113 4-3-4. DF Vectoring Altitudes 113 4-3-5. DF Vector Area 114 4-3-6. Distribution 114 4-3-7. Cancellation of DF Procedures 114

Section 4-4. Category II and III ILS 115 4-4-1. General 115 4-4-2. Action 116 4-4-3. NOTAM Requirements 117

Section 4-5. Departure Procedures (DP) 118 4-5-1. General 118 4-5-2. Diverse Vector Area (DVA) 118

Section 4-5. Departure Procedures (DP) 118 4-5-1. General 118 4-5-2. Diverse Vector Area (DVA) 118

Section 4-6. Standard Terminal Arrival (STAR) 119 4-6-1. Introduction 119 4-6-2. AeroNav Products Action 119

Section 4-7. RNAVProcedure Development 121 4-7-1. General 121 4-7-2. RNAV Approach Procedure Design 121 4-7-3. Developing RNAV Waypoint 123 4-7-4. RNAV Leg Types 125 4-7-5. RNAV Leg Type Descriptions 125 4-7-6. Final Approach Segment (FAS) Data 126 4-7-7. Remote Altimeter Setting for Baro-VNAV 126

01/09/2014 8260.19F

4-7-8. Critical Temperature 127 4-7-9. DME/DME Screening Model 127 4-7-10. Additional Documentation with Baro-VNAV 127

Chapter 5. Airspace 131

Chapter 5. Airspace 131

Section 5-1. Obstruction Evaluation (OE) 131 5-1-1. General 131 5-1-2. Responsibility and Processing of Form 7460-1 131 5-1-3. Review of Notices 131 5-1-4. Adjustments to Instrument Flight Procedures 131

Section 5-2. Designation of Controlled Airspace 132 5-2-1. General 132 5-2-2. Air Traffic Responsibility 132 5-2-3. AeroNav Products Action 132 5-2-4. Terminal Airspace 133

Section 5-3. Airport Airspace Analysis 169 5-3-1. General 169 5-3-2. Service Area OSG-FPT/Flight Standards Inputs 169 5-3-3. AFS performs the flight safety review of airport proposals 169 5-3-4. Service Area OSG-FPT is responsible for evaluation 169 5-3-5. Alterations of Airports or Heliports 170 5-3-6. Deactivation of Airports or Heliports 170 5-3-7. Assistance in Zoning Problems 171

Section 5-4. Restricted Areas 172 5-4-1. General 172 5-4-2. Letter of Procedures 172

Section 5-4. Restricted Areas 172 5-4-1. General 172 5-4-2. Letter of Procedures 172

Section 5-5. Establishment, Relocation, or Discontinuance of Radio Navigation Aids 173 5-5-1. Criteria and Guidelines 173 5-5-2. OSG-FPT Action 173 5-5-3. AFS Action 173

Chapter 6. Military Procedures , 175 6-1-1. General 175 6-1-2. Review and Coordination 175 6-1-3. FAA Acceptance 175 6-1-4. Assistance 175

Chapter 7. Planning 177

Chapter 7. Planning 177

Section 7-1. General 177 7-1-1. General 177

Section 7-2. Planning Standards 178 7-2-1. Planning Standards 178 7-2-2. Determination of Operational Benefits/Improvements 178

01/09/2014 8260.19F

Section 7-3. Safety Analysis 180 7-3-1. Performing a Safety Analysis 180

Section 7-4. Airway Planning 753 7-4-1. General 183

Section 7-4. Airway Planning 753 7-4-1. General 183

Section 7-5. Terminal Planning...'., 184 7-5-1. General 184 7-5-2. Requirements for Outer Compass Locators for New ILS Installations 184

Section 7-6. Airport Planning. 189 7-6-1. General 189

Section 7-7. Private Aid. 190 7-7-1. General 190

Section 7-8. Facilities andEquipment (F&E) Support 191 7-8-1. Support 191

Section 7-8. Facilities andEquipment (F&E) Support 191 7-8-1. Support 191

Chapter 8. Instrument Approach Procedures Data Transmittal System 193

Section 8-1. General 193 8-1-1. General 193

Section 8-2. FAA Form Use and Preparation 194 8-2-1. Use of FAA Forms 194 8-2-2. FAA Form Preparation 194 8-2-3. Course and Distance Information 195 8-2-4. Communications Data 196 8-2-5. Terminal Routes General 196 8-2-6. Terminal Fixes 200

Section 8-1. General 193 8-1-1. General 193

Section 8-3. Certification, Processing, and Review 202 8-3-1. General 202 8-3-2. Certification and Distribution of SIAPs 202 8-3-3. Cancellation/Suspension of Instrument Approach Procedures 204 8-3-4. Revisions to Instrument Flight Procedures (IFPs) 205 8-3-5. Processing 209 8-3-6. AeroNav Products Review of SIAPs and Charts 209 8-3-7. AeroNav Products Action 209

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

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

Section 8-5. Radio Fix and Holding Data Record, FAA Form 8260-2 277 8-5-1. Introduction 217 8-5-2. Preparation of Form 8260-2 217

Section 8-6. Completion of FAA Forms 8260-3/5 228 8-6-1. General 228 8-6-2. Terminal Routes 228 8-6-3. Lines 1 through 8 230 8-6-4. Takeoff and Alternate Minimums 237

01/09/2014 8260.19F

8-6-5. Minimums 238 8-6-6. Notes 249 8-6-7. Missed Approach 257 8-6-8. Additional Flight Data 262 8-6-9. Lower Blocks 268

Section 8-7. Standard Instrument Approach Procedure Data Record, FAA Form 8260-9 271 8-7-1. Preparation of Form 8260-9 271

Section 8-8. Completion of FAA Forms 8260-4/7/10 280 8-8-1. General 280 8-8-2. Form 8260-4, Radar 280 8-8-3. Form 8260-7A and Form 8260-7B 281 8-8-4. Form 8260-10, Continuation Sheet 283

Section 8-9. Terminal Arrival Area (TAA) Design - Documentation and Processing. 285 8-9-1. Instructions for 8260-Series Forms 285

Section 8-10. Transmittal ofAirways-Route Data, FAA Form 8260-16 290 8-10-1. Preparation of Form 8260-16.. 290

Appendix A. Administrative Information 321 1. Distribution 321 2. Terms, Definitions, and Acronyms 321 3. Acronyms and Abbreviations 321 4. Forms 328 5. Information Update 329

Appendix B. Flight Procedures References 331

Appendix C. Obstacle Accuracy Standards, Codes, and Sources 337 1. United States National Map Accuracy Standards 337 2. Accuracy Codes and Sources 338

Appendix D. FAA Form 8260-2, Data Worksheet 343

Appendix D. FAA Form 8260-2, Data Worksheet 343

Appendix E. Radio Fix and Holding Data Record, FAA Form 8260-2 345

Appendix F. ILS and RNAV Standard Instrument Approach Procedure,

FAA Form 8260-3 355

Appendix G. Radar-Standard Instrument Approach Procedure,

FAA Form 8260-4 ....357

Appendix H. Standard Instrument Approach Procedure, FAA Form 8260-5 359

Appendix H. Standard Instrument Approach Procedure, FAA Form 8260-5 359

Appendix I. Special Instrument Approach Procedure, FAA Form 8260-7A and Special Instrument Procedure Authorization, FAA Form 8260-7B.... 361

01/09/2014 8260.19F

Appendix J. Standard Instrument Approach Procedure, FAA Form 8260-9 365

Appendix J. Standard Instrument Approach Procedure, FAA Form 8260-9 365

Appendix K. Standard Instrument Approach Procedure Continuation Sheet,

FAA Form 8260-10.... 423

Appendix L. Final Approach Segment (FAS) Data Block Cyclic Redundancy Check

(CRC) Requirements 435

1. Fields needed for the Final Approach Segment (FAS) Data Block 435 2. Fields needed for integrity monitoring 435 3. Fields not included in the FAS Data Block 436 4. Explanation of data field entries 436

Appendix M. Final Approach Segment (FAS) Data Block Cyclic Redundancy

Appendix M. Final Approach Segment (FAS) Data Block Cyclic Redundancy

Check (CRC) Requirements for Helicopter Operations - RESERVED 447

Appendix N. ARINC 424 Database Codes 449

1. Waypoint Description Codes 449 2. Waypoint Description Code Definition/Description 450

Appendix O. Instrument Flight Procedures (IFP) Lifecycle. … 453

Appendix O. Instrument Flight Procedures (IFP) Lifecycle. … 453

1. This appendix consists of "basic" information pertaining to the "lifecycle" ofanFAA-developedlFP 453 2. Obtaining/meeting operations and/or aircraft approval requirements 453

01/09/2014 8260.19F

THIS PAGE IS INTENTIONALLY LEFT BLANK

Chapter 1. General Information

Section 1-1. General

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.

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.

1-1-3. Where You Can Find This Order. You can find this order on the FAA’s web site at: https://employees.faa.gov/tools_resources/orders_notices/.

1-1-4. What This Order Cancels. Order 8260.19E, Flight Procedures and Airspace, dated August 25, 2010, is canceled.

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

a. General.

(1) Revised paragraph numbering.

(2) Removed all guidance and references to Microwave Landing System (MLS) and Transponder Landing System (TLS).

(3) Removed all references and guidance regarding the use of Height Above Threshold (HATh) and Threshold Elevation (THRE) documentation due to reverting back to publishing minimums relative to Height Above Touchdown (HAT) and Touchdown Zone Elevation (TDZE).

b. Chapter 1.

(1) Section 1-2 Note. Made editorial changes as recommended by Office of Rulemaking, ARM- 26.

(2) Paragraph 1-2-2d. Added “and human-in-the-loop analysis” to first sentence and made some editorial changes.

(3) Paragraph 1-2-2e. Replaced “safety” with “levels of risk probabilities” and added: “This branch also develops Flight Systems Laboratory tools software applications (RNAV-Pro, RDVA-Pro, and the Engine Out Surface Evaluator [EOSE]) for use in RNAV/RNP procedure design and implementation.”

(4) Paragraph 1-2-4a. Updated Technical Operations Flight Inspection Services (AJW­ 3) responsibilities and removed last sentence; AJW-3 does not chair the National Airspace and Procedures Team (NAPT).

(5) Paragraph 1-2-5a(1). At the request of the National Flight Data Center (NFDC), added reference to AIRNAV database.

(6) Paragraph 1-2-5b(14). Moved NFDC responsibilities for Transmittal Letter development to AeroNav Products.

(7) Section 1-3. Added a Note to explain that all the responsibilities identified in this section are for information only and are there to assist procedure developers in knowing whom to contact for information in the performance of their duties.

(8) Paragraph 1-3-4. Added responsibility for Shared Service Organization (ATO-AIT). Added hyperlink to access standards for data resolution requirements which resolved NavLean Recommendation #9. Paragraphs re-numbered.

c. Chapter 2.

(1) Paragraph 2-1-1a. Changed directive reference to proper source and added guidance to inform the audience that information on the lifecycle of an Instrument Flight Procedure (IFP) can be found in appendix O.

(2) Paragraph 2-4-3d. Deleted last sentence; guidance already exists in Order JW-3 8200.6, paragraph 6c.

(3) Paragraph 2-5-1a. Added more background information regarding magnetic variation pertaining to area navigation (RNAV) procedures at the request of the FAA Aircraft Certification Division.

(4) Paragraph 2-5-1a Note. Revised with expanded text provided by Aircraft Certifications’ Avionics Systems Branch, AIR-130.

(5) Paragraph 2-5-2a(12)(a). Inserted clarification as recommended by the Performance based operations Rulemaking Committee (PARC) recommendations (Memo dated June 17, 2013) regarding magnetic variation applications.

(6) Paragraph 2-5-3a. Inserted suggested guidance as recommended by the Performance based operations Rulemaking Committee (PARC) recommendations (Memo dated June 17, 2013) regarding magnetic variation applications.

(7) Paragraph 2-5-3a Notes 1 and 2. Added notes as recommended by the Performance based operations Rulemaking Committee (PARC) recommendations (Memo dated June 17, 2013) regarding magnetic variation applications.

(8) Paragraph 2-5-3f(2). Clarified magnetic variation information for RNAV instrument procedures.

(9) Paragraph 2-6-2. Updated office responsible for the U.S. Notices to Airmen (NOTAM) System.

(10) Paragraph 2-6-2a. Editorial updates.

(11) Paragraph 2-6-3a. Explained what “EST” means.

(12) Paragraph 2-6-3b. Explained what “PERM” means.

(13) Paragraph 2-6-3b(6). Removed NFDC due to Transmittal Letter responsibility changes.

(14) Paragraph 2-6-3b(8). Added paragraph to indicate P-NOTAMs must be canceled when procedural change has been published.

(15) Paragraph 2-6-4. Minor editorial corrections throughout paragraph.

(16) Paragraph 2-6-4b. Added guidance to state that all times are Coordinated Universal Time (UTC).

(17) Paragraph 2-6-4c. Add “non-FAA” to “Service Provider.”

(18) Paragraph 2-6-4g. Updated NFDC responsibilities.

(19) Paragraph 2-6-5a. Added “or the non-FAA service provider” to first sentence.

(20) Paragraph 2-6-5b. Removed reference to Order 8260.3, U.S. Standard for Terminal Instrument Procedures (TERPS) paragraph that addressed NOTAMS; paragraph is being removed from Order 8260.3 with Change 26.

(21) Paragraph 2-6-5c Example. Editorial change made for clarity.

(22) Paragraph 2-6-7e. Editorial change made for clarity.

(23) Paragraph 2-6-8e. Inserted “224-day” reference to reiterate the required time limit.

(24) Paragraph 2-7-1d. Revised for clarity.

(25) Paragraph 2-7-2. Changed “AeroNav Products” to “non-FAA service provider.”

(26) Paragraph 2-8-1a. At the request of AeroNav Products, reference to the Procedure Tracking System (PTS) has been removed. Where this information is documented is left to the discretion of AeroNav Products.

(27) Paragraph 2-10-4a(2). At the request of the ATO, defined what is meant by “maintaining.”

(28) Paragraph 2-10-4a(6). Added “cancelations” to second sentence.

(29) Paragraph 2-10-4b. Added guidance regarding establishing Waypoints for RNAV procedures that appear on En Route Charts and are solely there to support the RNAV procedure. Also added guidance for when ATC needs to amend “Fix Use” to support ATC requirements.

(30) Paragraph 2-11-4c. Added exception to not apply horizontal and vertical accuracy values in the visual portion of final segment nor when evaluating the Glideslope Qualification Surface (GQS).

(31) Paragraph 2-11-4d. In order to eliminate any possible confusion on whether the exception to not apply horizontal and vertical accuracy values in the visual portion of final segment nor when evaluating the GQS also applied to required navigation performance (RNP) procedures; it is restated in this paragraph.

(32) Paragraph 2-11-5. Added exception to applying adverse assumption obstacle (AAO).

(33) Paragraph 2-11-5b & c. Revised “Exception” language to show that only the “obstacle” database that contains all surveyed information will be used and that terrain databases can be inhibited inside the surveyed areas.

(34) Paragraph 2-11-6b. Added guidance on datum substitution as specified in AFS-400 Memorandum, dated March 1, 2013, subject: “Clarification to Order 8260.58, United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design.”

(35) Paragraph 2-12-1. Added guidance to permit AFS-400 to determine if a waiver is not necessary for a deviation to policy and authorize the deviation using the Flight Standards approval process.

(36) Paragraph 2-12-2g. Deleted NFDC.

(37) Paragraph 2-12-4a. Revised first sentence upon recommendation from ATO.

d. Chapter 4.

(1) Paragraph 4-1-3d(2). Editorial for clarity, showing that the procedure turn area includes all types.

(2) Paragraph 4-1-6e(3). Revised to show lateral navigation (LNAV) criteria will be used for development of RNAV sidestep minima.

(3) Paragraph 4-6-2. Changed “verify” to “ensure” in several placed for language consistency.

(4) Paragraph 4-7-2. Changed “must” to “should” to make it a recommended option for RNAV procedures to be connected to the en route system.

(5) Paragraph 4-7-2a(5). Added option to use a standard terminal arrival route (STAR) terminating at an instrument approach fix (IAF) or IAF/IF or any point prior to the precision final approach fix (PFAF).

(6) Paragraph 4-7-2e Note. Revised text for clarity.

(7) Paragraph 4-7-6c. Revised text per Flight Inspection Services request to allow “FAS Data Block” coordinates to be other than World Geodetic System of 1984 (WGS-84) as long as the coordinates are the same as the ground survey data.

e. Chapter 5.

(1) Section 5-1. Removed portions that pertained to the responsibilities of the Obstruction Evaluation (OE) Group, AJV-15. Those responsibilities will be incorporated into Order JO 7400.2, Procedures for Handling Airspace Matters. Revised remaining text to provide basic guidance regarding OEs and geared for use by IFP developers.

(2) Paragraph 5-2-1a. Add reference to Terminal Arrival Areas (TAAs) must be contained within controlled airspace.

(3) Removed all formulas and examples incorporated into figures, placing them in the applicable paragraphs for easier reading.

f. Chapter 7.

(1) Paragraph 7-7-1a. Added reference to Office of Airports.

(2) Paragraph 7-1-1d. Added guidance to consider plume emitting devices and their effects on aircraft when designing instrument flight procedures.

(3) Paragraph 7-6-1b. Editorial changes per request of the Office of Airports.

g. Chapter 8.

(1) Paragraph 8-2-2c. Added SA CAT I and SA CAT II, as well as CAT II and CAT III procedures being combined on the same chart.

(2) Paragraph 8-2-5g Examples. Revised method used to describe NoPT arrivals over a navigational aid (NAVAID) facility per resolution agreed upon at the Aeronautical Charting Forum – Instrument Procedures Group, and addressed in Recommendation number 11-02-297, Airway “NoPT” Notes on Instrument Approaches.

(3) Paragraph 8-2-6d. Revised text at the request of Mission Support Services, AeroNav Products, AJV-3B, to support new FAA Form processing capabilities.

(4) Paragraph 8-3-2c. Deleted “Proposed Date” as an option per agreement reached at a meeting with AeroNav Products and the National Flight Data Center, which was held on

August 16, 2013 to discuss updating Order 8260.26, Establishing and Scheduling Civil Public- Use Standard Instrument Procedure Effective Dates.

(5) Paragraph 8-3-2e(1). Deleted reference to “Proposed Date.”

(6) Paragraph 8-3-3b. Added clarification for processing and new guidance on what to place in the “Additional Flight Data Block” when an Amendment is necessary after an instrument has been suspended and is being reinstituted.

(7) Paragraph 8-3-4. Note added to give flexibility when it is deemed necessary to cancel and reissue IFPs for reasons other than what is listed.

(8) Paragraph 8-3-5. Revised to change NFDC responsibilities to AeroNav Products responsibility.

(9) Paragraph 8-4-1f. Revised requirement to be more informative on alternatives considered prior to requesting a waiver and why those alternatives are not feasible. Additionally, Form 8260-1, Flight Procedures Standards Waiver, revised to support this change.

(10) Paragraph 8-4-1i and figure 8-4-1. Conversion of Form 8260-1 to a “report format” permitted the elimination of the “Continuation” portion of the Form. Paragraph letter sequence adjusted accordingly.

(11) Paragraph 8-5-2g Notes 1 & 2. Revised for clarity and added a pointer to another paragraph when an Office of Primary Responsibility (OPR) change might be needed.

(12) Paragraph 8-6-3b(1). Changed example “R-355” to R-180” for a more realistic portrayal.

(13) Paragraph 8-6-3c2(b). Updated example and deleted “by AeroNav Products” from the Note; this is the responsibility of all procedure developers not just AeroNav Products.

(14) Paragraph 8-6-5k(5). Clarified that the runway visual range (RVR) value will be derived from a checklist provided.

(15) Paragraph 8-6-5k(6). Added guidance to place a chart note indicating procedure not authorized when the control tower is closed.

(16) Paragraph 8-6-5m(2)(a). Add example of when this chart note would be used.

(17) Paragraph 8-6-5m(2)(g)&(h). Revised chart notes that restrict night operations in response to Aeronautical Charting Forum-Instrument Procedures Group Agenda Item: 09-02-291, Straight-in Minimums NA at Night.

(18) Paragraph 8-6-5m(6). At the request of AFS-470, revised Global Navigation Satellite System Landing System (GLS) restriction chart note to read: “Autopilot coupled approach NA below (decision Altitude)” and removed “GLS” from profile chart note.

(19) Paragraph 8-6-5m(6)(d). Added “Autopilot coupled approach NA.”

(20) Paragraph 8-6-5m(7)(c). Added guidance to support Order JO 7110.308, 1.5­ Nautical Mile Dependent Approaches to Parallel Runways Spaced Less Than 2,500 Feet Apart, operations. Adjusted letter sequence and added note to ensure the chart notes are documented in a specific sequence.

(21) Paragraph 8-6-5m(7)(e). Added GLS.

(22) Paragraph 8-6-6b. Added clarification text and example of a note that would construe regulating traffic and not be acceptable as a chart note.

(23) Paragraph 8-6-6h(5). Added text for clarity.

(24) Paragraph 8-6-6n. Note added to prevent numerical values and that chart producers will obtain the information from the applicable source.

(25) Paragraph 8-6-7g. Removed “or as directed by ATC” as part of Missed Approach instructions and clarified guidance.

(26) Paragraph 8-6-8h. Converted “Note” into two separate paragraphs to show that computing offset for conventional procedures is different for RNAV (GPS) and RNP procedures.

(27) Paragraph 8-6-9b(1). Revised last sentence to change from stating “Various Heliports” to using a “primary heliport” and list all heliports in the “Additional Flight Data Block”.

(28) Paragraph 8-6-9d(4). Removed reverence to a specific type of procedure, thus allowing for additional procedure types to be applied as they become authorized.

(29) Paragraph 8-6-9d(5). Added guidance to support “Converging” instrument procedures.

(30) Paragraph 8-6-9f. Revised to change NFDC responsibilities to AeroNav Products responsibility.

(31) Paragraph 8-7-1b(12). Revised paragraph to remove reference to “PDA” that is no longer used and made editorial corrections at the request of AeroNav Products, AJV-3B.

(32) Paragraph 8-7-1b(20) Examples. Reinserted data unintentionally omitted in previous version of this order.

(33) Paragraph 8-7-1c(10) Example. Removed reference to “ISA LOW” and “ISA HIGH” in the “Critical Temperatures” box.

(34) Section 8-9. Added this section with material extracted from Order 8260.58, United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design, regarding documentation of Terminal Arrival Areas.

(35) Paragraph 8-10-1. Expanded guidance to reference 14 CFR Part 71.

(36) Paragraph 8-10-1c(1). Changed “semi-annually” to annually and added reference to 14 CFR Part 95 IFR altitudes.

h. Appendix A.

(1) Updated acronyms and abbreviations.

(2) Revised table A-2, for Form name 8260-7B to read “Special Instrument Procedure Authorization.”

i. Appendix B. Updated references.

j. Appendix C. Paragraph 2b(1). Revised Department of Commerce accuracies according to input received from the ATO Mission Support Services, Geographic Services Group, Terrain and Obstacle Data Team.

k. Appendix D. Added guidance to Block 7 to allow for “No Change” to be annotated when there is no change to the fix itself.

l. Appendix I. Revised Form 8260-7B title.

m. Appendix J. Made corrections to all Form 8260-9, Standard Instrument Approach Procedure Data Record, examples, removing “ISA LOW” and “ISA HIGH” where applicable.

n. Appendix L.

(1) Paragraph 4h. Changed “Tech Ops” to “Spectrum Engineering.”

(2) Paragraph 4i. Changed RPI information pertaining to GBAS operations.

(3) Paragraph 4q(1)-(4). Expanded guidance for when a Vertical Descent Angle (VDA) is used for an LP procedure.

(4) Paragraph 4r. Corrected guidance and example regarding establishing course width at threshold values.

o. Appendix O. Per NavLean Recommendation #19, added this appendix to show the basic, start to finish, process for an Instrument Flight Procedure, referred to as the IFP Lifecycle.

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.

Section 1-2. Responsibilities

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 Title 14, Code of Federal Regulations (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 requests for waivers of standards.

b. The Flight Operations Branch (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 United States instrument flight operations standards and to foster standards with a level of safety consonant with those of the United States.

c. The Flight Procedure Standards Branch (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. The Flight Operations Simulation Branch (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, Air Traffic Organization (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 International Civil Aviation Organization (ICAO).

e. The Flight Systems Laboratory (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 RNAV/RNP procedure design and implementation.

f. The Flight Procedure Implementation and Oversight Branch (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 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. In addition to flight procedure oversight, 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. The Performance Based Navigation Branch (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 Operations Specification (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. The Regional Flight Standards Divisions (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 all weather 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 7400.2, Procedures for Handling Airspace Matters, and dictate involvement in a broad range of technical evaluations (i.e., determining feasibility for CAT II/III operations utilizing 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 area navigation (RNAV) visual flight procedures.

(8) Coordinating with Airports Division in the approval or denial of modifications airport standards, providing written safety assessment of end-around taxiway (EAT) proposals/use and declared distance concepts (see Order 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 AeroNav Products 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. 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 in-flight inspection of air navigation facilities throughout the United States and its territories. It is 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 AJW-3 element responsible for flight inspection of navigation aids and flight procedures in support of the NAS. The group initiates and completes investigative remedial action with respect to any deficiency or reported hazard, including restrictions or emergency revisions to procedures. It maintains liaison with AeroNav Products, as well as other FAA offices, civil and military interests, to ensure consideration of all

requirements relating to the procedural use of navigation facilities. It maintains a suitable record system reflecting the status of each flight procedure with required supporting data.

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

a. Aeronautical Information Management Office (AJV-2) is directly responsible for managing the agency’s program to provide aeronautical information services to ensure the flow of information necessary for safety, regularity, and efficiency of air navigation. This office is charged with the responsibility for collecting, collating, validating, maintaining, and disseminating aeronautical data regarding the United States and its territories. It is also a source for technical assistance to the Aeronautical Navigation Products Office (AeroNav Products), AJV-3 regarding database accuracy standards, content, and format.

(1) The National Flight Data Center, (NFDC), is the principal element within AJV-2 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-2 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 Aeronautical Information Services through the ICAO.

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

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

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

(c) Verifying source data for as-built obstacles and assigning accuracy codes that reflect the reliability of the reported obstacle's vertical height and horizontal position.

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

(e) Managing the requirements and technology for Telephony, NASR, AIRNAV, Airport GIS, TPSS, AMDB, and the Airspace Design and Analysis Center (SDAT, TFR, SAA, Controlled) databases and infrastructure.

b. Aeronautical Navigation Products (AeroNav Products) (AJV-3) is the FAA element 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 (DVAs).

(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 AeroNav Products.

(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 AeroNav Products.

(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) Establishes procedures to ensure operational data are included in the NASR database.

(13) Analyzing obstruction evaluations to determine the effects on current and planned instrument flight operations, minimums, and/or flight altitudes of all civil, joint-use, and United States 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.

1-2-7. Transferring Instrument Procedure Maintenance Responsibilities. Instrument procedures are normally maintained by AeroNav Products; however, special procedures may be maintained by the proponent. The proponent must show that they are capable of meeting all the requirements stipulated in Order 8260.60, Special Instrument Procedures. Procedures currently maintained by the FAA may be released to the proponent for maintenance after the following requirements have been met:

a. Proponent submits a written request to AFS-400 to seek approval to assume maintenance responsibilities from AeroNav Products. This request must indicate how the requirements specified in Order 8260.60 will be met.

b. AFS-400 responds to the proponent with approval or disapproval. If the transfer is approved, the proponent will contact AeroNav Products to address the following:

(1) Establish transfer date.

(2) Inform the RAPT that the maintenance responsibilities for (specified) instrument procedures have been transferred to the proponent.

Note: Include the (maintenance) point-of-contact to ensure all potential correspondence (e.g., OE studies, etc.) from members of the RAPT reaches the proper parties.

(3) Renegotiate reimbursable agreement regarding all required continuing services (e.g., Flight Inspection, etc.).

(4) Coordinate transfer of documentation files to include all applicable 8260-series forms and general correspondence that pertains to the procedure(s).

(5) Inform AFS-460 (Specials Office) that transfer of maintenance responsibilities has been completed.

Section 1-3. Instrument Procedure Development Software Responsibilities

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, Flight Procedures and Airspace; 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 Navigation (AeroNav) Products (AJV-3) Responsibility. This is the office of primary interest that is responsible for overall functional management of the FAA instrument procedures software and for ensuring the implementation of AFS-420 defined software requirements.

a. AeroNav Products is 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.

(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) 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 a ll 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 C FR 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.

c. Aeronautical Information Management Office (AJV-2) is responsible for establishing and maintaining the AIRNAV database in support of instrument procedure software requirements.

1-3-4. Information Technology Shared Service Organization (AIT) 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 at: http://ea.faa.gov/DataAndInformation/airTransportInfrastructure/documents/ifpDataPrecisionRes olutionRequirements.html

1-3-5. Office of Information Services (AMI-1). The Office of Information Services, AMI-1, 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. The utilization of 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, AIO-1, 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.

THIS PAGE IS INTENTIONALLY LEFT BLANK

THIS PAGE IS INTENTIONALLY LEFT BLANK

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.

Section 2-1. General

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, Flight Procedures Management Program. It may be a request from a state, city, airport manager, or an individual. It may also be from an air carrier, air taxi, military, commercial operator, Air Traffic Control (ATC), or Flight Standards Service (AFS) personnel. General information on the lifecycle process associated with IFPs can be found in appendix O.

b. Requirements for approval of instrument approach procedures are contained in Order 8260.3, U.S. Standard for Terminal Instrument Procedures (TERPS), Volume 1, chapter 1.

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

2-1-2. Air Traffic Letters of Agreement. When letters of agreement affect or include flight procedures, they must be coordinated between ATC facilities and AeroNav Products.

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

b. Copies of letters of agreement received in AeroNav Products 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, AeroNav Products 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 AeroNav Products 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) JO 7110.10, Flight Services.

(2) JO 7110.65, Air Traffic Control.

(3) JO 7210.3, Facility Operation and Administration.

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

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

Section 2-2. Aeronautical Charts

Section 2-2. Aeronautical Charts

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

a. AeroNav Products 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, the Airport Obstruction Chart (OC) 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 United States 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, AeroNav Products Weekly Obstacle Memo, Digital Terrain Elevation Data (DTED), Digital Elevation Model (DEM), etc., in addition to onsite obstacle assessment evaluations, where necessary. The Sectional Aeronautical Chart (scale 1:500,000) and the visual flight rules (VFR) Terminal Area Chart (scale 1:250,000) are good supporting source documents; however, they may not depict all current information because of the extended charting cycle.

b. Charting requirements for inclusion in a flight inspection package should be determined from the Flight Inspection Policy Team [see Order 8200.1, United States Standard Flight Inspection Manual].

2-2-2. Aeronautical Charts and Publications.

a. Aeronautical charts used for air navigation are generally of two groups: visual flight rules (VFR) charts and instrument flight rules (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 standard instrument approach procedure (SIAP), textual and graphic departure procedure (DP), standard terminal arrival (STAR), and Charted Visual Flight Procedure charts.

b. The primary publication, which contains basic flight information related to instrument operations in the National Airspace (NAS), is the Aeronautical Information Manual (AIM). The primary publication serving as a pre-flight and planning guide for use by United States nonscheduled operators, business, and private aviators flying outside of the United States 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. AeroNav Products 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. AeroNav Products is responsible for the accuracy and completeness of flight data submitted by that office for publication. Procedure specialists should review the resulting published United States Government charts to ensure correct portrayal. AeroNav Products serves as the focal point for questions regarding the procedural data published on these charts.

e. AeroNav Products is responsible for ensuring that United States 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 should forward the information to AFS-460, or AeroNav Products, Resource Planning and Management Support (AJV-3A). AIM and AIP discrepancies should be referred to the Production Technology & ATC Products Group (AJV-36).

Section 2-3. Environmental Requirements

Section 2-3. Environmental Requirements

2-3-1. Noise Abatement. The establishment of noise abatement procedures is the responsibility of the Air Traffic Organization. However, the Flight Standards Service has an input from an aircraft operational standpoint. These procedures should be coordinated between the appropriate regional Flight Standards Division (RFSD) and the Operational Support Group, Flight Procedures Team (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, Procedures for Handling Airspace Matters, chapter 32, Environmental Matters, is required to meet the environmental compliance requirements of the Agency under the National Environmental Policy Act (NEPA).

Section 2-4. Facility Utilization and Monitoring

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 figures 2-4-1, 2-4-2, and 2-4-3].

a. DME/VOR/VORTAC/TACAN.

Facility Usable Height Usable Class Above Facility Distance

(Miles) T 12,000 and below 25 L 18,000 and below 40 H 60,000-45,000 100 Below 45,000-18,000 130 Below 18,000-14,500 100 Below 14,500 40

Note: All elevations shown are with respect to the station’s site elevation.

Figure 2-4-1. Standard High Altitude Service Volume

Chapter 2

Chapter 2

Figure 2-4-2. Standard Low Altitude Service Volume

Chapter 2

Figure 2-4-3. Standard Terminal Service Volume

Chapter 2

b. Nondirectional Beacon (NDB).

Facility Height Above Distance Class Facility (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) 4,500 and below 18 Localizer (BC) 4,500 and below 18 Glide Slope (2°-4°) varies with angle 10

2-4-3. Requests for Expanded Service Volumes (ESV).

a. When ATC requires use of navigational aids (NAVAIDs) above/beyond limitations cited in paragraphs 2-4-3a through 2-4-3d, 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 AeroNav Products.

b. AeroNav Products 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 AeroNav Products approval.

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

d. Facility rotation due to magnetic variation change should have no effect on coverage; however, radials used will change. AeroNav Products initiates a change action via the Spectrum Management web site (ESVMS) on the date the rotation is effective.

e. Describe holding patterns by radial, distance, altitude, and the maximum length holding pattern leg.

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-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 Air Traffic Organization is responsible for issuing Notice to Airmen (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-4b.

(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 minimum en route altitude (MEA) to higher MEA (can be used as a break to a lower MEA).

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

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

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

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

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

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

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

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

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

e. DP Turn Points. The 75 MHz markers must not be used to identify turn points on departure procedures. See Order 8260.46, Departure Procedure (DP) Program, paragraph 2-1-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 Magnetic Variation Values.

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

a. Background. The National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), and the National Geodetic Survey (NGS), for all areas of the United States and its territories for application to navigation charts and maps, is the source for magnetic variation (MV) information and tools for establishing magnetic variation. Changing values for MV are tabulated and published on a 5-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 navigational aid and airport as the Magnetic Variation 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 magnetic variation value stored in their navigational database, though other values are sometimes applied. As such, it is entirely possible that the magnetic variation applied by the RNAV system is different than the magnetic variation 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) AeroNav Products.

(2) Military Organizations.

(3) National Flight Data Center (NFDC).

(4) Western, Central, and Eastern Technical Operations.

(5) Western, Central, and Eastern OSG-FPTs.

(6) Regional Airports Divisions.

2-5-2. Responsibilities.

a. AeroNav Products.

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

(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 National Flight Data Digest (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: navigational aids, airports, instrument flight procedures; and for coordination and liaison between AeroNav Products and the applicable Air Traffic Service Area OSG-FPTs. 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.

(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 navigational aids 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 (in AJV-21) 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 navigational aids 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, obstacle departure procedures (ODPs), standard instrument departures (SIDs), standard terminal arrival routes (STARs), and

any other application to instrument flight procedures. Use the MV of Record (or as officially changed) to develop instrument flight procedures - regardless of the MV shown on the airport diagram chart or similar product being used.

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

(a) Modify all fixes and instrument approach procedures (IAPs). Modify all Title 14 Code of Federal Regulations, Part 95 (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) Navigational aids not supporting en route structure:

(a) Initiate implementation of the nearest future Epoch Year MV in accordance with paragraph 2-5-3a, 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-8n and 8-6-8o].

(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 and direction finder (DF) procedures when the airport MV of Record is changed. If the DF is located at an off-airport site, obtain the MV for the antenna site; include MV and Epoch Year in the lower right corner of the Form 8260-10 (see section 4-3).

(13) Army Facilities.

(a) Accomplish MV changes for United States 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; navigational aids, airports, instrument flight procedures.

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

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

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

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

(6) Notify AeroNav Products 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 AeroNav Products 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-2a, 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-8n and 8-6-8o].

(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 AeroNav Products to obtain the MV of Record or MV assignments for new or relocated facilities to be applied to navigational aids or airports under Navy jurisdiction.

(2) Coordinate with AeroNav Products to determine impact of MV changes for both military and public facilities.

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

(4) Notify AeroNav Products of changes to Navy, non-NAS facilities, assigned MV and the effective date of those changes in order to allow AeroNav Products 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) Navy navigational facilities within the NAS:

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

(b) Notify AeroNav Products when MV changes are required. Allow sufficient time for modification of FAA fixes and IAPs as necessary. National Flight Data Center. When notified by AeroNav Products 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. 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.

e. 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 AeroNav Products, 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. The identification and selection of navigational aids 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 facility 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-6-9e(2)(e)].

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. When the difference between the MV of Record and the nearest future Epoch Year value of any navigational aid or airport is three degrees or more, the MV of Record must be changed to the nearest future Epoch Year value. When the difference is less than three degrees, consider implementing the nearest future Epoch Year value when workload permits and approved by the Regional Airspace and Procedures Team (RAPT). Factors to consider include whether the navigational aid is isolated or in close proximity to one or more other facilities, whether on airport or away from an airport, and the impact on instrument flight procedures. For CAT II/III ILS facilities, the intent is to keep these facilities as closely aligned with the actual [as predicted by the World Magnetic Model (WMM)] magnetic variation at the airport. Maintain the assigned magnetic variation value for these facilities within ±1 degree of the current airport magnetic variation. If it exceeds one degree, assign the ILS the current magnetic variation (to the nearest whole degree) and list it as the next future epoch year value.

Note 1: The NOAA WMM estimates MV at any location and day within the five-year validity window of the model. For example, the WMM for 2010 provides MV values for all locations for January 1, 2010 through December 31, 2014. The nearest future Epoch year to be used after January 1, 2010 would be specified as 2015, and the corresponding MV typically based on the December 31, 2014 value. However, the assigned MV may be listed as using the 2015 epoch even though the value may be associated with a date earlier in the validity period of the model. This would occur when it is required in order to maintain the assigned value for a CAT II/III facility within one degree of the current value.

Note 2: At airports that have CAT II/III instrument procedures, the one-degree tolerance effectively applies to the airport MV, the MV for all facilities on the airport, and the MV for all RNAV procedures required to use the aerodrome MV as indicated in paragraphs 2-5-3(b), 2-5-3(d), and 2-5-3(f) below.

Note 3: At locations that have CAT II/III instrument procedures, do not apply future Epoch Year MV values that would create a MV of Record that exceeds one degree of the current, actual airport MV.

b. Facilities on Airports. At airports with localizer(s) or more than one navigational aid, the MV at the airport reference point (ARP) must be designated and assigned to all facilities at that airport, including all components of the ILS.

c. MV versus OC Chart Value. Where the assigned MV of Record differs from the MV shown on the Obstruction Chart (OC), the assigned MV of Record must be used in the development of instrument flight procedures.

d. Runway heading must be assigned the same MV as the airport.

Note: The actual runway heading is published on airport diagrams to allow pilots to obtain a compass bearing check during runway line-up. This value may differ from the value computed during the assigned variation.

e. At major airport terminal areas, the ARP MV of Record at the designated controlling airport may be used in determining the MV applied to all navigational aids serving the terminal areas.

f. Standard Rules for Applying Magnetic Variation to True Radials, Bearings, and Courses.

(1) Ground Based and Radar Facilities.

(a) Utilize the facility Magnetic Variation of Record to determine magnetic tracks, and courses.

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

(2) RNAV.

(a) Instrument Approach Procedures (IAPs)/DPs/STARs. Magnetic variation is applied to any track/course used in an RNAV instrument procedure and it must be the magnetic variation of the aerodrome of intended landing or departure. Some aircraft navigation systems use a “reference NAVAID” for obtaining magnetic variation 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), a NAVAID that has the same assigned magnetic variation as the airport magnetic variation.

(b) Holding on IAPs/DPs/STARs. RNAV track/course information is based on the true track/course from one fix to a succeeding fix. To determine the magnetic track/course, apply the published magnetic variation of the aerodrome, or the en route VOR or NDB assigned

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

(c) Holding on Routes or Stand-Alone. For RNAV only holding patterns not associated with an instrument procedure or a VOR or NDB used as the holding fix, determine the magnetic variation by using the magnetic declination (variation) for the holding fix latitude/longitude. This information may be calculated using the National Geophysical Data Center (NGDC) website.

Section 2-6. Notices to Airmen (NOTAMs)

Section 2-6. Notices to Airmen (NOTAMs)

2-6-1. General. NOTAMs provide timely knowledge, to flyers and other aviation interests, of information or conditions, which are essential to safety of flight. NOTAMs pertaining to IFPs are effective upon issuance and must remain in effect until the pertinent aeronautical charts are amended or the condition requiring the NOTAM ends. This section deals primarily with procedures for issuing Flight Data Center (FDC) NOTAMs when required to maintain the accuracy and currency of terminal and en route IFPs. Also, see Order 8260.3.

2-6-2. United States NOTAM System. The United States NOTAM System (USNS) has been established to provide aviators with the current status of the NAS. This system is under the purview of FAA’s Air Traffic Organization, Vice President of System Operations Services, Flight Services, Safety and Operations Policy Group (AJR-B1). Management and operational guidance is contained in Order JO 7930.2, Notices to Airmen (NOTAMs). The following is a brief summary of the use of FDC NOTAMs and related issues due to IFP changes, NAVAID outages, and government aeronautical chart corrections.

Continue reading ↓ 120 of 973 passages shown