Radar Vectors
FAA Order Cancelled Issued Aug 27, 2007 AFS-420 301 pages Copy saved Nov 18, 2026

Order 8260.19D Flight Procedures and Airspace

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

Official source ↗ Open PDF

Distribution: A-W(SY/PO/UA/AR/ND/AS/FS/AT/AF)-3; ATA-100 (15 Cys); AJW-351 (15 Cys); AJW-32 (200 Cys); AJR-33 (10 Cys); AMA-200 (12 Cys); A-X(FS/AT/AF/AS)-3; A-FFS-0 (STD); AEU-1 (10 Cys); A-FAF-O (STD); ZVN-826; Special Military and Public Addressees

Initiated By: AFS-420

This order provides guidance for all personnel in the administration of the Flight Procedures and Airspace Program. It defines responsibilities, establishes criteria, and provides standards to ensure effective and orderly processing of all types of procedures actions.

The Flight Procedure Standards Branch, AFS-420, of the Flight Technologies and Procedures Division, AFS-400, is responsible for the rulemaking process of the Flight Procedures Program which includes development, application, and oversight of the National Flight Procedures Program and development of criteria pertinent to designing instrument flight procedures.

Procedures personnel must use sound judgment, imagination, and initiative in carrying out their assigned responsibilities and duties. They are encouraged to recommend improved methods of operation. Due to the extensive revisions incorporated in this Order and to provide a sufficient amount of time for instrument procedure specialists to be trained, an effective date has been established as specified in paragraph 103. Original Signed By Carol Giles James J. Ballough Director, Flight Standards Service

08/27/2007

National Policy

SUBJ: Flight Procedures and Airspace

ORDER 8260.19D

ORDER 8260.19D

RECORD OF CHANGES

8260.19D

CHANGE SUPPLEMENTS CHANGE SUPPLEMENTS

TO OPTIONAL USE TO OPTIONAL USE BASIC BASIC

FAA Form 1320-5 SUPERSEDES PREVIOUS EDITION

Page i

TABLE OF CONTENTS

Page CHAPTER 1. ADMINISTRATIVE SECTION 1. GENERAL 100. Purpose … 1-1 101. Distribution … 1-1 102. Cancellation … 1-1 103. Effective Date … 1-1 104. Explanation of Changes … 1-1 105. Forms … 1-4 106. Terms, Definitions, and Acronyms … 1-5 107. Information Update … 1-5 108.-109. Reserved … 1-5 SECTION 2. RESPONSIBILITIES 110. Flight Standards Service (AFS-1) … 1-6 111. Flight Technologies and Procedures Division (AFS-400) … 1-6 112. Regional Flight Standards Divisions (AXX-200) … 1-7 113. Technical Operations, Aviation System Standards Office (AJW-3) … 1-8 114. Aeronautical Information Management Group (AJR-32) … 1-9 115. Individual … 1-10 116. Transferring Instrument Procedure Maintenance Responsibilities … 1-10 117.-119. Reserved … 1-10 SECTION 3. INSTRUMENT PROCEDURE SOFTWARE DEVELOPMENT RESPONSIBILITIES 120. Background … 1-11 121. Flight Procedure Standards Branch’s Responsibility … 1-11 122. Technical Operations Aviation System Standards Office’s Responsibility … 1-11 123. Office of Information Services (AMI-1) … 1-12 124. Office of Assistant Administrator for Information Services (AIO-1) … 1-12 125. Vice President for Technical Operations (AJW-O) … 1-12 126.-199. Reserved … 1-12 CHAPTER 2. GENERAL PROCEDURES SECTION 1. GENERAL 200. General … 2-1 201. Requests for Public-Use Instrument Flight Procedures … 2-1 202. Air Traffic Letters of Agreement … 2-1 203. Airport Lighting and Visual Aids … 2-1 SECTION 2. AERONAUTICAL CHARTS 204. Use of Maps and Charts … 2-2 205. Aeronautical Charts and Publications … 2-2 SECTION 3. ENVIRONMENTAL REQUIREMENTS 206. Noise Abatement … 2-4 207. Environmental Impacts … 2-4

TABLE OF CONTENTS

Page ii

TABLE OF CONTENTS (Continued)

Page SECTION 4. FACILITY UTILIZATION AND MONITORING 208. Frequency Service Volumes … 2-5 209. ATC Usable Distance and Altitude Limitations … 2-5 210. Requests for Expanded Service Volumes (ESV) … 2-6 211. Utilization of Localizers as En Route Aids … 2-7 212. Monitoring of Navigation Facilities … 2-7 213. Utilization of Monitoring Categories … 2-7 214. Utilization of 75 Mhz Markers … 2-8 SECTION 5. IMPLEMENTING EPOCH YEAR MAGNETIC VARIATION (MV) 215. General … 2-9 216. Responsibilities … 2-9 217. Guidelines … 2-11 218.-219. Reserved … 2-12 SECTION 6. NOTICES TO AIRMEN (NOTAMs) 220. General … 2-13 221. National Notice to Airmen System … 2-13 222. FDC T-NOTAM Preparation, Review, and Transmittal … 2-13 223. FDC P-NOTAM Preparation, Review, and Transmittal … 2-14 224. Instrument Approach and Textual Departure Procedure NOTAMs … 2-15 225. Graphic ODP, SID, and STAR NOTAM Preparation, Review, and Transmittal … 2-15 226. General NOTAM D Actions … 2-16 227. Airway NOTAMs … 2-17 228. FDC NOTAMs for Special Instrument Approach Procedures (Specials) … 2-17 229. NOTAM Content … 2-18 SECTION 7. QUALITY/STANDARDIZATION OF INSTRUMENT FLIGHT PROCEDURES 230. NFPO Action … 2-20 231. AFS-460 Action … 2-20 232.-239. Reserved … 2-20 SECTION 8. PERIODIC REVIEW OF INSTRUMENT FLIGHT PROCEDURES 240. General … 2-21 241. NFPO Action … 2-21 242.-249. Reserved … 2-22 SECTION 9. COMMUNICATIONS AND WEATHER 250. Communications Requirements … 2-23 251. Use of UNICOM … 2-23 252. Automatic Altimeter Setting and Weather Reporting Systems … 2-23 253.-259. Reserved … 2-23

Page iii

TABLE OF CONTENTS (Continued)

Page SECTION 10. NAVIGATIONAL FIXES 260. General … 2-24 261. Reporting Points … 2-24 262. Unplanned Holding at Designated Reporting Points … 2-24 263. Requests for Navigational Fixes … 2-24 264. Naming Navigational Fixes … 2-24 265. Documenting Navigational Fixes … 2-25 266. Correlation of Navigational Fixes and Changeover Points (COPs) … 2-25 267. Minimum Reception Altitudes (MRA) … 2-26 268. Flight Inspection … 2-26 269. Maximum Authorized Altitudes (MAA) … 2-26 SECTION 11. OBSTACLE DATA 270. General … 2-27 271. Obstacle Data Sources … 2-27 272. Obstacle Data Accuracy Standards for Instrument Procedures … 2-27 273. Accuracy Standards Application … 2-28 274. Controlling Obstacles … 2-29 275. Vertical Datums … 2-31 276.-279. Reserved … 2-31 SECTION 12. WAIVER OF STANDARDS 280. General … 2-32 281. Waiver Processing … 2-32 282. Waivers for Special Instrument Approach Procedures … 2-32 283. Periodic Review of Waivers … 2-33 284. Cancellation of Waivers … 2-33 285.-289. Reserved … 2-33 CHAPTER 3. EN ROUTE PROCEDURES SECTION 1. GENERAL 300. General … 3-1 301. Publication … 3-1 302.-309. Reserved … 3-1 SECTION 2. CRITERIA APPLICATION AND DEVELOPMENT 310. Criteria Application … 3-2 311. Development of Criteria … 3-2 312.-319. Reserved … 3-2

Page iv

TABLE OF CONTENTS (Continued)

Page SECTION 3. ESTABLISHMENT OF EN ROUTE AIRSPACE 320. Relationship of COPs to Airspace Dimensions … 3-3 321. Relationship of MEAs to Controlled Airspace Floors … 3-3 322.-329. Reserved … 3-3 SECTION 4. SUBSTITUTE EN ROUTE FLIGHT PROCEDURES 330. General … 3-4 331. Format … 3-4 332. Facilities Used … 3-4 333. Controlled Airspace … 3-4 334. Flight Inspection … 3-4 335. Planning and Coordination … 3-4 336. Processing … 3-8 337. Periodic Review … 3-8 338. Distribution … 3-8 339. Reserved … 3-8 SECTION 5. OFF-AIRWAY ROUTES 340. Establishment … 3-9 341. Listing … 3-9 342. Off-Airway Data … 3-9 343. Processing Data to NFDC … 3-9 344.-349. Reserved … 3-9 SECTION 6. NEW OR REVISED NATIONAL AIRSPACE SYSTEM ROUTES 350. Definition … 3-10 351. Coordination Procedures … 3-10 352. Publication of Procedural Data … 3-10 353.-359. Reserved … 3-10 SECTION 7. MINIMUM VECTORING ALTITUDE (MVA) AND MINIMUM IFR ALTITUDE (MIA) CHARTS 360. Chart Preparation … 3-11 361. Areas of Consideration … 3-11 362. Obstacle Clearance … 3-11 363. Obstacle Clearance Reduction … 3-12 364. Chart Review and Approval … 3-12 365. Emergency Obstruction Video Map (EOVM) … 3-13 366.-369. Reserved … 3-13 CHAPTER 4. TERMINAL PROCEDURES SECTION 1. GENERAL 400. General … 4-1 401. Categories of Instrument Approach Procedures … 4-1 402. Airspace Requirements … 4-1

Page v

TABLE OF CONTENTS (Continued)

Page 403. Contractual Use of Private Facilities … 4-1 404. TERPS Application … 4-1 405. Sidestep Maneuvers … 4-6 406. Temporarily Displaced/Relocated Threshold Procedures … 4-7 407.-419. Reserved … 4-7 SECTION 2. STANDARD INSTRUMENT APPROACH PROCEDURES (SIAP) 420. General … 4-8 421. Coordination of Terminal Instrument Procedures … 4-8 422. Radar Instrument Approach Procedures … 4-8 423.-429. Reserved … 4-8 SECTION 3. VISUAL DESCENT POINT (VDP) 430. Establishment … 4-9 431. Multiple Altimeter Sources … 4-9 432. FAA Form 8260-9 Entries … 4-9 433.-439. Reserved … 4-9 SECTION 4. SPECIAL INSTRUMENT PROCEDURES PROCESSING 440. Initiating a Request for Special Instrument Procedures … 4-10 441. Processing Requests … 4-10 442. Procedure Package Content … 4-14 443. Minor Revisions of Special Procedures … 4-15 444. Cancellation of Special Procedures … 4-15 445. Distribution … 4-16 446.-449. Reserved … 4-16 SECTION 5. DIRECTION FINDER (DF) PROCEDURES 450. General … 4-19 451. Format … 4-19 452. Application of Criteria … 4-19 453. DF Vectoring Altitudes … 4-19 454. DF Vector Area … 4-19 455. Distribution … 4-20 456. Cancellation of DF Procedures … 4-20 457.-459. Reserved … 4-20 SECTION 6. CATEGORY II AND III ILS 460. General … 4-21 461. Action … 4-21 462. NOTAM Requirements … 4-22 463.-469. Reserved … 4-22 SECTION 7. DEPARTURE PROCEDURES (DP) 470. General … 4-23 471.-479. Reserved … 4-23

Page vi

TABLE OF CONTENTS (Continued)

Page SECTION 8. STANDARD TERMINAL ARRIVAL (STAR) 480. Introduction … 4-24 481. NFPO Action … 4-24 482.-489. Reserved … 4-24 SECTION 9. RNAV PROCEDURE DEVELOPMENT 490. General … 4-25 491. RNAV Approach Procedure Design … 4-25 492. Developing RNAV Waypoint … 4-26 493. RNAV Leg Types … 4-27 494. RNAV Leg Type Descriptions … 4-27 495. Final Approach Segment (FAS) Data … 4-28 496. Remote Altimeter Setting for Baro-VNAV … 4-28 497. Critical Temperature … 4-28 498. DME/DME Screening Model … 4-29 499. Additional Documentation with Baro-VNAV (LNAV/VNAV and RNP), Local Area Augmentation System (LAAS) and/or Wide Area Augmentation System (WAAS) Instrument Approach Procedures … 4-29 CHAPTER 5. AIRSPACE SECTION 1. OBSTRUCTION EVALUATION (OE) 500. General … 5-1 501. Responsibility and Processing of FAA Form 7460-1 … 5-1 502. Review of Notices … 5-1 503. Obstructions Under Subpart C, 14 CFR Part 77 … 5-2 SECTION 2. DESIGNATION OF CONTROLLED AIRSPACE 504. General … 5-3 505. Air Traffic Responsibility … 5-3 506. NFPO Action … 5-3 507. Terminal Airspace … 5-3 SECTION 3. AIRPORT AIRSPACE ANALYSIS 508. General … 5-18 509. NFPO/AFS Inputs in Establishment of Airports and Heliports … 5-18 510. Alterations of Airports or Heliports … 5-19 511. Deactivation of Airports or Heliports … 5-19 512. Assistance in Zoning Problems … 5-19 SECTION 4. RESERVED 513.-516. Reserved … 5-20

Page vii

TABLE OF CONTENTS (Continued)

Page SECTION 5. RESTRICED AREAS 517. General … 5-21 518. Letter of Procedures … 5-21 519. Reserved … 5-21 SECTION 6. ESTABLISHMENT, RELOCATION, OR DISCONTINUANCE OF RADIO NAVIGATION AIDS 520. Criteria and Guidelines … 5-22 521. NFPO Action … 5-22 522. AFS Action … 5-22 523.-599. Reserved … 5-22 CHAPTER 6. MILITARY PROCEDURES 600. General … 6-1 601. Review and Coordination … 6-1 602. FAA Acceptance … 6-1 603. Assistance … 6-1 604.-699. Reserved … 6-1 CHAPTER 7. PLANNING SECTION 1. GENERAL 700. General … 7-1 SECTION 2. PLANNING STANDARDS 701. Planning Standards … 7-2 702. Determination of Operational Benefits/Improvements … 7-2 SECTION 3. SAFETY ANALYSIS 703. Performing a Safety Analysis … 7-4 SECTION 4. AIRWAY PLANNING 704. General … 7-6 SECTION 5. TERMINAL PLANNING 705. General … 7-7 706. Requirements for Outer Compass Locators for New ILS Installations … 7-7 SECTION 6. AIRPORT PLANNING 707. General … 7-12

Page viii

TABLE OF CONTENTS (Continued)

Page SECTION 7. PRIVATE AID 708. General … 7-13 SECTION 8. FACILITY AND EQUIPMENT (F&E) SUPPORT 709. Support … 7-14 710.-799. Reserved … 7-14 CHAPTER 8. INSTRUMENT APPROACH PROCEDURES DATA TRANSMITTAL SYSTEM SECTION 1. GENERAL 800. General … 8-1 SECTION 2. FORM USE AND PREPARATION 801. Use of Forms … 8-2 802. Form Preparation … 8-2 803. Course and Distance Information … 8-3 804. Communications Data … 8-3 805. Terminal Routes General … 8-4 806. Terminal Fixes … 8-6 807.-809. Reserved … 8-7 SECTION 3. CERTIFICATION, PROCESSING, AND REVIEW 810. General … 8-8 811. Certification and Distribution of SIAPs … 8-8 812. Cancellation of Instrument Approach Procedures … 8-10 813. Minor Revisions to SIAPs … 8-10 814. Processing … 8-10 815. NFPO Review of SIAPs and Charts … 8-10 816. NFPO Action … 8-10 817.-819. Reserved … 8-11 SECTION 4. RESERVED 820.-829. Reserved … 8-12

SECTION 5. FLIGHT PROCEDURES STANDARDS WAIVER, FAA FORM 8260-1 830. Preparation of FAA Form 8260-1, Flight Procedures Standards Waiver … 8-13 831.-839. Reserved … 8-14

SECTION 6. RADIO FIX AND HOLDING DATA RECORD, FAA Form 8260-2 840. Introduction … 8-17 841. Preparation of FAA Form 8260-2 … 8-17 842.-849. Reserved … 8-23

Page ix

TABLE OF CONTENTS (Continued

Page SECTION 7. COMPLETION OF FAA FORMS 8260-3/5 850. General … 8-24 851. Terminal Routes … 8-24 852. Lines 1 through 8 … 8-26 853. Takeoff and Alternate Minimums … 8-30 854. Minimums … 8-31 855. Notes … 8-38 856. Missed Approach … 8-43 857. Additional Flight Data … 8-47 858. Lower Blocks … 8-50 859. Reserved … 8-53 SECTION 8. STANDARD INSTRUMENT APPROACH PROCEDURE DATA RECORD, FAA FORM 8260-9 860. Preparation of FAA Form 8260-9 … 8-54 861.-869. Reserved … 8-59 SECTION 9. COMPLETION OF FORMS 8260-4/7/10 870. General … 8-60 871. Form 8260-4, Radar … 8-60 872. Form 8260-7, Special Instrument Approach Procedure … 8-61 873. Form 8260-10, Continuation Sheet … 8-62 874.-879. Reserved … 8-62 SECTION 10. TRANSMITTAL OF AIRWAYS – ROUTE DATA, FAA FORM 8260-16 880. Preparation of FAA Form 8260-16 … 8-63 881.-889. Reserved … 8-65 APPENDIX 1. ACRONYMS AND ABBREVIATIONS (5 Pages) APPENDIX 2. FLIGHT PROCEDURES REFERENCES (5 Pages) Orders and Notices … 3 Advisory Circulars … 4 Title 14, Code of Federal Regulations (CFR) … 5 Other Publications … 6 APPENDIX 3. OBSTACLE ACCURACY STANDARDS, CODES, AND SOURCES (5 Pages) 100. United States National Map Accuracy Standards … 3 101. Accuracy Codes and Sources … 3 APPENDIX 4. DATA WORKSHEET FOR FAA FORM 8260-2, RADIO FIX AND HOLDING DATA RECORD (3 Pages) Data Worksheet Instructions … 3 Sample DATA Worksheet for FAA Form 1320-2, … 4

Page x

TABLE OF CONTENTS (Continued)

Page APPENDIX 5. RADIO FIX AND HOLDING DATA RECORD, FAA FORM 8260-2 (10 Pages) Sample FAA Forms 8260-2 (Front and Back) … 3 thru 11 APPENDIX 6. ILS AND RNAV STANDARD INSTRUMENT APPROACH PROCEDURE, FAA FORM 8260-3 (3 Pages) Sample FAA Forms 8260 3 (Front and Back) … 3 thru 4 APPENDIX 7 RADAR - STANDARD INSTRUMENT APPROACH PROCEDURE, FAA FORM 8260-4 (3 Pages) Sample FAA Form 8260-4 (Front and Back) … 3 thru 4 APPENDIX 8. STANDARD INSTRUMENT APPROACH PROCEDURE, FAA FORM 8260-5 (3 Pages) Sample FAA Forms 8260-5 (Front and Back Sides) … 3 thru 4 APPENDIX 9. SPECIAL INSTRUMENT APPROACH PROCEDURE, FAA FORM 8260-7 (3 Pages) Sample FAA Form 8260-7 (Front and Back Sides) … 3 thru 4 APPENDIX 10. STANDARD INSTRUMENT APPROACH PROCEDURE DATA RECORD, FAA FORM 8260-9 (9 Pages) Sample FAA Forms 8260-9 (Front and Back Sides) … 3 thru 10 APPENDIX 11. STANDARD INSTRUMENT APPROACH PROCEDURE CONTINUATION SHEET, FAA FORM 8260-10 (13 Pages) Sample FAA Form 8260-10 (Front and Back Sides) … 3 thru 14 APPENDIX 12. FINAL APPROACH SEGMENT (FAS) DATA CYCLIC REDUNDANCY CHECK (CRC) REQUIREMENTS (10 Pages) … 3 thru 11 APPENDIX 13. ARINC 424 DATABASE CODES (5 Pages) … 3 thru 6

CHAPTER 1. ADMINISTRATIVE

CHAPTER 1. ADMINISTRATIVE

SECTION 1. GENERAL

100. PURPOSE. This order provides guidance to all FAA personnel for the administration and accomplishment of the FAA Flight Procedures and Airspace Program. 101. DISTRIBUTION. This order is distributed in Washington headquarters to the branch level in the Offices of Aviation Policy and Plans, Aviation Research, Airport Safety and Standards, the Air Traffic Organization (Safety, En Route and Oceanic Services, Terminal Services, System Operations Services, and Technical Operations Services), and Flight Standards Service; to the Aeronautical Information Management Group, the National Flight Procedures Office, Airspace and Rules Group, the National Aeronautical Charting Office, and the National Airway Systems Engineering Group; to the Regulatory Standards Division; to the branch level in the regional Flight Standards and Airports Divisions; to the Air Traffic and Technical Operations Service Areas, to all Flight Inspection Field Offices; to the Europe, Africa, and Middle East Area Office; to all Flight Standards Field Offices; Special Mailing List ZVN-826; and Special Military and Public Addressees. 102. CANCELLATION. a. Order 8260.19C, Flight Procedures and Airspace, dated September 16, 1993, is canceled. b. Order 8260.33, Instrument Approach Procedures Automation (IAPA) Program, dated March 30, 1982, is canceled. 103. EFFECTIVE DATE. November 26, 2007. 104. EXPLANATION OF CHANGES. a. Management titles, organizational identifications, routing codes, and responsibilities updated to reflect the current organizational structure.

SECTION 1. GENERAL

b. Chapter 1. (1) Paragraph 111. Updates and clarifies the responsibilities of the Flight Technologies and Procedures Division (AFS-400. (2) Paragraph 113. Updates and clarifies the responsibilities of the Technical Operations Aviation Standards Office. (3) Paragraph 114b(4). Clarifies NOTAM responsibility for the Aeronautical Information Management Group. (4) Paragraph 116. Policy for transferring special instrument procedure maintenance responsibilities added. (5) Section 3. Responsibilities for instrument procedure software development clarified. c. Chapter 2. (1) Paragraph 201. Guidance for submission of requests for public-use procedures and assignment of priority clarified. (2) Paragraph 205d. Clarifies that the National Flight Procedures Office (NFPO) is responsible for reviewing government procedure charts to ensure correct portrayal and is the focal point for questions concerning procedural data on the charts. Also clarifies that the National Flight Data Center (NFDC) serves as the focal point for questions concerning non-procedural data. (3) Paragraph 205e. Adds responsibility that the National Aeronautical Charting Office (NACO) ensures the U.S. Government aeronautical charts conform to Inter- Agency Air Cartographic Committee (IACC) specifications. (4) Paragraph 210f. Adds guidance for preparing and processing expanded service volume (ESVs).

8260.19D

(5) Paragraph 213c. Adds specification that 75 MHz markers must not be used to denote turn points on departure procedures (DPs). (6) Paragraph 216a(3). Adds NACO responsibility to revise en route charts to apply yearly magnetic variation (MV) change values to area navigation (RNAV) Q routes. (7) Paragraph 221b. Clarifies the use of permanent and temporary Flight Data Center (FDC) NOTAMs. (8) Paragraph 222a. Assigns the NFPO the responsibility to develop procedures for T-NOTAM quality control, transmittal, cancellation, and follow-up actions. (9) Paragraph 222b. Assigns the NFPO the responsibility for chart review and cancellation of FDC NOTAMs. (10) Paragraph 223a. Assigns the NACO the responsibility for issuing FDC P-NOTAMs and developing procedures for P-NOTAM quality control, transmittal, cancellation, and follow-up actions. (11) Paragraph 226e. Adds requirement for the NFDC to advise the NFPO whenever a NOTAM D relating to a NAVAID outage is canceled and published in the AFD. (12) Paragraph 226f. Adds guidance and examples for FDC NOTAMs to support area navigation (RNAV) substitution. (13) Paragraph 226i. Provides additional guidance on suspension of Category (CAT) II/III minimums. (14) Paragraph 228. Adds guidance to support FDC NOTAMs for Special instrument approach procedures (Specials). (15) Paragraph 241a(8). Adds process for coordinating proposed instrument flight procedure (IFP) changes. (16) Paragraph 264a(4). Expands policy for missed approach point identification.

(17) Paragraph 264a(11). Provides guidance on naming PFAF. (18) Paragraph 271. Provides information regarding the content of the digital obstacle file (DOF) of manmade obstructions maintained by the NACO. (19) Paragraph 274. Provides guidance on application of an Adverse Assumption Obstacle (AAO) under Title 14 Code of Federal Regulations (14 CFR) Part 77.13 and specifies areas that are exempt from AAO application. (20) Paragraph 275. Clarifies guidance relating to vertical datums. d. Chapter 3. (1) Paragraph 300a. Adds the term Air Traffic Service (ATS) Routes and includes RNAV as a navigation source. (2) Paragraph 320b. Adds note to clarify the rounding process for minimum en route altitudes (MEAs) to the nearest 100 ft that must not cause less than the required obstacle clearance. (3) Paragraph 351a. Provides additional guidance for coordinating procedures for new or revised National Airspace System (NAS) routes. (4) Paragraph 360. Makes reference to Notice 8260.64, Radar Approaches and Minimum Vectoring Altitudes - Current Guidance and Criteria. (5) Paragraph 361. Clarifies areas of consideration for both MVA and MIA charts. (6) Paragraph 362a. Adds requirement to include AAO additive to terrain values for both MVA and MIA charts. (7) Paragraph 362b. Clarifies floor of controlled airspace application for both MVA and MIA charts, and requires NFPO to ensure correct application.

(8) Paragraph 362c. Clarifies rounding process for MVAs and MIAs to ensure correct ROC application. (9) Paragraph 363. Clarifies policy for obstacle clearance reductions and requires a record of approval to include rationale. (10) Paragraph 364a. Expands paragraph to allow an approved automation tool for MVA and MIA development and submission. e. Chapter 4. (1) Paragraph 404e(1). Specifies that, when using an alpha naming convention, “Z” will be used for the procedure with the lowest minimums. (2) Paragraph 404i. Expands NoPT application for feeder routes. (3) Paragraph 430a. Requires a visual descent point (VDP) for localizer and LNAV when combined with a vertically guided approach procedure. (4) Paragraph 431. Adds guidance for VDP application when using backup remote altimeter source. (5) Paragraph 441. Entire paragraph updated to clarify and expand responsibilities of the Flight Standards District Office (FSDO)/ Certificate Management Office (CMO), Regional Flight Standards Division-All Weather Operations Program Manager (RFSD-AWOPM), National Flight Procedures Office (NFPO), and AFS- 200/400/800 when processing Special instrument procedure requests (Specials). (6) Paragraph 442a(2). Expands NOTAM policy for Specials. (7) Paragraph 442a(11). Requires the proponent/operator to provide the RAPT a graphic portrayal when submitting a Special. (8) Paragraph 442b. Specifies the minimum requirements for Special procedure packages when submitted to AFS-400 for approval.

(9) Paragraph 442c. Requires a copy of the Special Procedure Checklist when submitting a Special for AFS approval. (10) Paragraph 443. Adds a new paragraph to cover minor revisions of Special procedures. (11) Paragraph 491b(1). Requires RNAV procedure design to an ILS-equipped runway to emulate the ILS procedure to the extent possible. (12) Paragraph 491d. Adds option to design RNAV required navigation performance (RNP) procedures with different RNP values in the final approach segment. (13) Paragraph 492b. Adds guidance for documenting on 8260-series forms the waypoint description codes for all waypoint fixes used in RNAV procedure designs. (14) Paragraph 492d(7). Adds guidance for RNAV stepdown fixes within procedure segments. (15) Paragraph 497. Provides supplementary guidance on critical temperatures for barometric vertical navigation (Baro VNAV) operations. (16) Paragraph 499. Entire paragraph updated to provide additional guidance for documenting information for LNAV/VNAV, RNP, and WAAS procedures. f. Chapter 5. (1) Section 4, Controlled Firing Areas (CFAs).

Removed at the request of the Airspace and Rules Group. CFAs are approved by the applicable Air Traffic Service Center office. They are subject to an aeronautical review and the Service Center issues an approval letter that specifies the conditions and safety precautions that must be used. Guidance for CFAs is published in Order 7400.2, Procedures for Handling Airspace Matters, chapter 27. Minimum required precautionary measures are set forth in Order 7400.2, paragraph 27-3-2. Order 7400.2 does not address coordination of CFA proposals with the NFPO. Order 7400.2 will be amended to ensure that Service Centers coordinate proposed CFAs

8260.19D

with Flight Standards to obtain input on local VFR operations. g. Chapter 6. (1) Paragraph 600. Adds statement that “the FAA will accept responsibility for the development and/or publication of military procedures when requested to do so by the appropriate military service through an interagency agreement.” (2) Paragraph 603. Adds guidance for military to contact AFS-420 for assistance on instrument procedures design, criteria, etc. h. Chapter 7. (1) Paragraph 705c. Provides guidance concerning waiver action to support new construction. i. Chapter 8. Refines and expands guidance for preparing and completing forms for

various instrument approach procedures. It also contains some new sample forms. j. Appendix 1. New appendix added to provide a listing of acronyms and abbreviations used throughout the Order. k. Appendix 2. Flight procedures references updated. l. Appendix 3. Obstacle accuracy standards, codes, and sources updated. m. Appendices 5 through 11. Sample forms updated to reflect revised format. n. Appendix 13. FAS data block cyclic redundancy check (CRC) requirements updated to reflect requirements for LAAS and LPV procedures. 105. FORMS. a. The following forms are provided in electronic form for use in the development and maintenance of flight procedures. FAA FORM NUMBER TITLE

FAA Form 8260-1 Flight Procedures Standards Waiver

FAA Form 8260-2 Radio Fix and Holding Data Record

FAA Form 8260-3 ILS-Standard Instrument Approach Procedure

FAA Form 8260-4 Radar Standard Instrument Approach Procedure

FAA Form 8260-5 Standard Instrument Approach Procedure

FAA Form 8260-7 Special Instrument Approach Procedure

FAA Form 8260-9 Standard Instrument Approach Procedure Data Record

FAA Form 8260-10 Standard Instrument Approach Procedure (Continuation Sheet)

FAA Form 8260-11 U.S. Army/U.S. Air Force ILS Standard Instrument Approach Procedure

FAA Form 8260-12 U.S. Army/U.S. Air Force Radar Standard Instrument Approach Procedure

FAA Form 8260-13 U.S. Army/U.S. Air Force Standard Instrument Approach Procedure

FAA Form 8260-15A Takeoff Minimums and Textual Departure Procedures (DP)

FAA Form 8260-15B Graphic Departure Procedures (DP)

FAA Form 8260-15C Departure (Data Record)

FAA Form 8260-15D Departure Procedure (Continuation)

FAA Form 8260-16 Transmittal of Airways/Route Data FAA Form 8260-20 U.S. Army/U.S. Air Force Standard Instrument Approach Procedure (Continuation Sheet)

FAA Form 8260-21A U.S. Army/U.S. Air Force Departure Procedures/Takeoff Minimums

FAA Form 8260-21B U.S. Army/U.S. Air Force Standard Instrument Departure (SID) FAA Form 8260-21C U.S. Army/U.S. Air Force Departure (Data Record) FAA Form 8260-21D U.S. Army/U.S. Air Force Departure Procedure (Continuation) b. Computer Generated Forms. Most FAA forms used in the development of instrument procedures can be automated through the use of an approved electronic forms software package. (1) Implementation. The implementation of this system will reduce the errors and tedium of completing procedures forms either by hand or by the typewriter. This system also allows information to be extracted from sources such as text files and other databases. (2) Use of Automated Forms. This automated process allows each user to fill in forms completely and accurately, and to print the forms. The Flight Procedure Standards Branch, AFS-420, provides administrative control over any modification of the automated forms. Direct any recommendations for changes or modifications to AFS-420 with a courtesy copy to the National Flight Procedures Office Automation Support. (3) Equipment Requirements. Each user office must have access to the appropriate hardware/software to use automated electronic forms software. Contact NFPO for more specific requirements. (4) System Description. This electronic form processor has a visual interface and allows each user to work with forms using windows, pictures, and menus on a screen. The completed screen data and form may be printed on bond paper. c. All referenced orders are applicable to the current edition.

106. TERMS, DEFINITIONS, AND ACRONYMS. For the purpose of this order, flight procedures are identified as the functions for predetermining safe and practical methods of navigating aircraft that prescribe intended flight tracks, operational altitudes, and arrival/departure minimums. Flight procedures are subdivided into six general categories as follows: departure procedure, en route, instrument approach, missed approach, holding, and fix descriptions. The following words have the meaning shown: a. May − action is permissible. b. Must/Shall − action is mandatory. c. Should - action is desirable. d. Will − Indicates a presumption that action is to be taken. Appendix 1 provides an alphabetical listing of all the acronyms and abbreviations used throughout this order. 107. INFORMATION UPDATE. For your convenience, FAA Form 1320-19, Directive Feedback Information, is included at the end of this revision to note any deficiencies found, clarification needed, or suggested improvements regarding the contents of this revision. When forwarding your comments to the originating office for consideration, please provide a complete explanation of why the suggested change is necessary.

8260.19D

108.-109. RESERVED.

8260.19D

SECTION 2. RESPONSIBILITIES

110. 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. 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. 111. FLIGHT TECHNOLOGIES AND PRO- CEDURES DIVISION (AFS-400). a.

SECTION 2. RESPONSIBILITIES

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 Part 95 and standard instrument approach procedures under 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 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 FAA Form 8260-10, Special Instrument Approach Procedure, as required, through the Procedures Review Board. Provides technical representation to ICAO on matters related to instrument flight operations, and maintains liaison with foreign civil aviation operational and technical authorities to encourage the acceptance of U.S. instrument flight operations standards and to foster standards with a level of safety consonant with those of the United States. c.

The Flight Procedures 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 and cartographic programs, and is the primary interface for industry on matters relating to instrument procedures criteria. The branch assists 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, that provides simulation of new, emerging, or modified Communications, Navigation, and Surveillance (CNS) technologies and procedures in support of flight safety, accomplished through computer modeling, flight and controller simulators, and/or industry aircraft. This branch manages the Flight

Operations Simulation Laboratory comprised of flight simulators and ATC controller stations that can be linked to provide real time pilot/controller interface and data collection to meet the safety studies' and risk analyses' data requirements. These simulations are used to support AFS offices, ATO, airports, regions, the aviation industry, and FAA executives who seek objective and subjective safety analysis and assessments to enhance flight operations, standards, capacity, and aviation safety within the NAS and international organizations such as ICAO. e. The Flight Systems Laboratory, AFS-450, is the principal element within the division that analyzes and quantifies the safety 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. 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 thirdparty procedure development, maintenance, and flight evaluation/verification of instrument flight procedures. Oversees organizational responsibilities relating to the implementation of instrument flight procedure standards, criteria, policy, software, and flight inspection policy. Develops national and international standards and criteria governing the operational use of instrument flight procedures.

Defines responsibilities, establishes policy, and provides standards for orderly processing of all instrument flight procedure actions, international, third-party, and FAA. Evaluates Instrument Flight Pro-cedures from operational and technical viewpoints, provides necessary coordination, and recommends final approval or disapproval of Special instrument flight procedures and waiver of standards for all instrument flight procedures.

g. The Performance Based Flight Systems 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 FAA Form 8260-10, 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 OpSpecs 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. 112. REGIONAL FLIGHT STANDARDS DIVISIONS (AXX-200). a. The Regional Flight Standards Divisions (RFSD) manage and direct 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. b. The all weather operations program 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. (2) Providing technical evaluations in support of regional airspace programs to determine the effect on visual flight operations.

8260.19D

(3) Coordinating the RFSD portion of assigned foreign instrument approach procedures programs. (4) Coordinating the RFSD involvement in CAT II and III approvals including approval of the associated Surface Movement Guidance System plan. (5) Providing the operational input on matters related to regional capacity studies and airport operational safety initiatives. (6) Performing airport/airspace evaluations to address operational safety issues in coordination with the Airports Division, as necessary. (7) Providing the consolidated RFSD position for review of charted visual flight procedures. (8) Coordinating with Airports Division in the approval or denial of modifications to airport standards. (9) Providing operational review and comments for Air Traffic Technical Operations Service Area’s submission of a NAS Change Proposal (NCP). (10) When requested by the Flight Procedures Field Office (FPFO), assists in developing the equivalent level of safety for an NFPO originated procedures waiver. 113. TECHNICAL OPERATIONS AVIATION SYSTEM STANDARDS OFFICE (AJW-3). a.

AJW-3 is the principal element within the Technical Operations Services (AJW-O) directly responsible for the in-flight inspection of air navigation facilities and for the development and maintenance of instrument flight procedures 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. AJW-3 supports the Air Traffic Organization’s Obstruction Evaluation Services Team, AJR-322, obstruction evaluation and airport airspace analysis (OE/AAA) program

in assessing IFR impact of proposed construction. The Director of AJW-3 also serves as the chairperson of the National Airspace and Procedures Team (NAPT) under Order 8260.43, Flight Procedures Management Program. b. The National Flight Procedures Office (NFPO) is the FAA element responsible for the development, maintenance, quality assurance, and technical approval of public-use instrument procedures. It is also responsible for quality assurance and operations support, as requested, for NAS related products. Upon completion of instrument procedures development, the division forwards completed documentation to the Flight Inspection Operations Group (FIOG) for flight inspection and operational approval. It establishes procedures to ensure operational data is included in the National Airspace System Resources (NASR) database. The NFPO includes a sub-element at each Air Traffic Service Area office identified as a Flight Procedures Field Office.

NFPO/FPFO 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. (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 National Airspace System is to be commissioned, de-commissioned, or altered.

8260.19D

(7) Coordinating the input for the planning and development of regional and Air Traffic Service Area F&E budget submissions and programming actions. (8) Analyzing obstruction evaluations to determine the effects on current and planned instrument flight operations, minimums, and/or flight altitudes of all civil, joint-use, and U.S. Army instrument procedures in accordance with current policy. (9) Evaluating regional airport and airspace changes for impact on instrument flight procedures. (10) Determining the necessity for environmental impact studies as required by current policy. (11) Acting as the focal point for flight inspection problems within the region. c. The Flight Inspection Operations Group (FIOG) 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 the NFPO, 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. d. The National Aeronautical Charting Office (NACO) is the AJW-3 element responsible for the production and distribution of aeronautical charts and related publications and products. This includes the publication of Standard Instrument Approach Procedure (SIAP), Departure Procedure (DP), Standard Terminal Arrival (STAR) charts, Airport Diagrams, and Special Graphics. NACO responsibilities include but are not limited to: (1) Selecting and evaluating source data for final chart compilation. (2) Validating geographical positions, distances, and bearings.

(3) Maintaining liaison with elements of FAA to support safe and accurate portrayal of charting data. (4) Evaluating obstacle source data to certify accuracy codes as built. (5) Providing civilian charts in support of military requirements. (6) Providing international charting support to selected foreign countries. 114. AERONAUTICAL INFORMATION MANAGEMENT GROUP (AJR-32). a. This is the principal element within the Air Traffic Organization, Office of System Operations (AJR-O) 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 group 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 AJW-3 regarding database accuracy standards, content, and format. b.

The National Flight Data Center, (NFDC), is the principal element within AJR-32 with respect to maintaining the National Airspace System Resources (NASR) database and for disseminating information relating to the NAS. NFDC responsibilities include but are not limited to: (1) Publishing the daily National Flight Data Digest (NFDD) to promulgate additions, changes, and deletions to nonregulatory elements of the NAS. (2) 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 actions submitted for action, and to identify and correct items in non-conformance with applicable directives.

8260.19D

(3) Validating submitted data with the National Airspace System Resources (NASR) Database and resolving contradictions. (4) Reviewing and tracking NOTAMs regarding amendments, cancellations, and corrections to instrument procedures and NAVAIDs in the NAS. (5) Compiling NOTAMs for publication in the Notices to Airmen Publication (NTAP). (6) Managing the development and assignment of five-letter fix names and NAVAID/airport identifiers. (7) Promulgating SIAPs and ODPs with assigned effective dates in a bi-weekly transmittal letter and completing necessary requirements for publication in Part 97. (8) Issuing, on a predetermined schedule, amendments to Part 95. (9) Maintaining copies of 8260- and 7100-series forms that support public use SIAPs, fixes, airways, STARs, and DPs. 115. 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.

116. TRANSFERRING INSTRUMENT PRO- CEDURE MAINTENANCE RESPONSIBILITIES. Instrument procedures are normally maintained by the NFPO; however, Special procedures may be maintained by the proponent. The proponent must show that they are capable of meeting all the requirements stipulated in chapter 4, paragraph 442.

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 the NFPO. This request must indicate how the requirements specified in paragraphs 442a(1) through (4) will be met. b. AFS-400 responds to the proponent with approval or disapproval. If the transfer is approved, the proponent will contact the NFPO to address the following: (1) Establish transfer date. (2) Inform the Regional Airspace Procedures Team (RAPT) that the maintenance responsibilities for (specified) instrument procedures have been transferred to the proponent.

Note: Include the (maintenance) point-ofcontact 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. 117.-119. RESERVED.

8260.19D

SECTION 3. INSTRUMENT PROCEDURE DEVELOPMENT

SECTION 3. INSTRUMENT PROCEDURE DEVELOPMENT

SOFTWARE RESPONSIBILITIES

120. 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. 121. 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. 122. TECHNICAL OPERATIONS AVIATION SYSTEM STANDARDS OFFICE’S RESPONSI- BILITY. AJW-3 is the office of primary interest and is responsible for overall functional management of the FAA instrument procedures software and for ensuring the implementation of AFS-420 defined software requirements. a. The National Flight Procedures Office 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.

SOFTWARE RESPONSIBILITIES

(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) The NFPO is responsible for assuring system software is in conformance with established software requirements. b. The NFPO Quality Oversight and Technical Advisory Team is responsible for assuring the successful ongoing operation of the data system. In the performance of these responsibilities, the team must: (1) Establish and maintain a positive change control management system to assure that all changes to the operational instrument procedure software system are cost effective and are coordinated among all parties who use the FAA instrument procedure software. (2) Develop necessary guidelines for the control and dissemination of data from the FAA instrument procedure software and other assigned systems.

8260.19D

Chap 1 Page 1-13 (and 1-14) Par 122

(3) Authorize release of data in special cases where guidelines are not available. (4) Provide for coordination in data systems where several program elements share primary operational interest. (5) Establish priorities for task assignments, scheduling, and utilization of personnel and physical resources. (6) Assure system configuration, documentation, and reliability. (7) Conduct extensive operational testing and debugging, to assure system software is in conformance with Order 8260.3 and other appropriate directives, advisory circulars, and 14 CFR provisions. Conduct final system certification of software before release to users through coordination with AFS-420. (8) Review national user requirements and approve system modifications. (9) Ensure that the provisions of Order 1370.82, Information Systems Security Program, are complied within the security control of computer programs and associated documentation. c. The Flight Inspection Operations Group is responsible for establishing and maintaining the Aviation System Standards Information System (AVNIS) in support of instrument procedure software requirements. 123. 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. 124. OFFICE OF ASSISTANT ADMINIS- TRATOR FOR INFORMATION SERVICES (AIO- 1). The Office of Assistant Administrator for Information Services, AIO-1, will develop governing policies and responsibilities for automatic data processing (ADP) program management in accordance with Order 1370.52, Information Resources Policy. 125. VICE PRESIDENT FOR TECHNICAL OPERATIONS (AJW-O). The Vice President for Technical Operations 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. 126.-199. RESERVED.

CHAPTER 2. GENERAL PROCEDURES

CHAPTER 2. GENERAL PROCEDURES

SECTION 1. GENERAL

200. GENERAL. 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. 201. REQUESTS FOR PUBLIC-USE INSTRU-MENT FLIGHT PROCEDURES. a. Requests for approval and/or establishment of instrument flight procedures may originate from many different sources. 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 AFS personnel. See Order 8260.3, Volume 1, paragraph 121. b. All requests for public-use instrument flight procedures received by any FAA office must be forwarded to the Flight Procedures Field Office (FPFO) for further handling under Order 8260.43, Flight Procedures Management Program. Requirements for approval of instrument approach procedures are contained in Order 8260.3, Volume 1, chapter 1. c. Procedures with specific effective dates, and other urgent projects, will be assigned priorities by the National Flight Procedures Office (NFPO). All other projects will be processed as workload permits, by the NFPO in order of receipt. 202. AIR TRAFFIC LETTERS OF AGREE- MENT. When letters of agreement affect or include flight procedures, they must be coordinated between ATC facilities and the NFPO.

SECTION 1. GENERAL

a. When these letters are received, the NFPO must review them to ensure compatibility with published or planned flight procedures. b. Copies of letters of agreement received in the NFPO 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, the NFPO 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 the NFPO is a party to the agreement, it is not a signatory and does not approve or disapprove the agreement. 203. AIRPORT LIGHTING AND VISUAL AIDS. a. Operation of airport lighting and visual aids is contained in the following orders: (1) 7110.10, Flight Services. (2) 7110.65, Air Traffic Control. (3) 7210.3, Facility Operation and Administration. b. Installation criteria are contained in Order 6850.2, Visual Guidance Lighting Systems. c. Refer to appendix 1, Flight Procedures References, for other applicable orders and advisory circulars.

SECTION 2. AERONAUTICAL CHARTS

SECTION 2. AERONAUTICAL CHARTS

204. USE OF MAPS AND CHARTS. a. The NFPO 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 U.S. Geological Survey provide an excellent source for determining terrain elevation. For efficiency in procedure design and flight inspection, 1:100,000 scale planimetric/topographical (topo) charts are also authorized.

Use other data sources such as Digital Obstruction File (DOF), Aviation System Standards Information System (AVNIS), National Aeronautical Charting Office (NACO) Weekly Obstacle Memo, Digital Terrain Elevation Data (DTED), Digital Elevation Model (DEM), etc., in addition to on-site obstacle assessment evaluations, where necessary. The Sectional Aeronautical Chart (scale 1:500,000) and the visual flight rules (VFR) Terminal Area Chart (scale 1:250,000) are good supporting source documents; however, they may not depict all current information because of the extended charting cycle. b. 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, paragraph 6.11]. 205. AERONAUTICAL CHARTS AND PUBLICATIONS. a. Aeronautical charts used for air navigation are generally of two groups: 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 NAS, is the Aeronautical Information Manual (AIM). The primary publication serving as a preflight and planning guide for use by U.S. 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 System Operations Airspace and AIM Office, Publications Group (AJR-31). c. NFPO 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.

The NFPO is responsible for the accuracy and completeness of flight data submitted by that office for publication. Procedure specialists should review the resulting published U.S. Government charts to ensure correct portrayal. The NFPO serves as the focal point for questions regarding the procedural data published on these charts. e. The 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. f. NACO is responsible for ensuring that U.S. Government Aeronautical Charts conform to Interagency Air Cartographic Committee (IACC) specifications. 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 the NACO Requirements and Technology Staff. AIM and AIP discrepancies should be referred to the ATO Publications Group, AJR-31.

SECTION 3. ENVIRONMENTAL REQUIREMENTS

SECTION 3. ENVIRONMENTAL REQUIREMENTS

206. 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 regional FPFO. The RFSD must review noise abatement procedures for aircraft performance characteristics and operational safety considerations. The regional FPFO 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.

207. ENVIRONMENTAL IMPACTS. Order 1050.1, Environmental Impacts: Policies and Procedures, describes the requirements for documentation of environmental impact or lack of impact concerning actions taken by regional FPFOs. In particular, chapter 3 of the document defines actions that require an environmental assessment or a declaration of categorical exclusion [see also paragraph 303]. Technical Operations Aviation System Standards, AJW-3, will normally act as a responsible federal official (RFO) for all AJW-3 and non-AJW-3 developed procedures. In such capacity, AJW-3 must apply national environmental standards and policies. However, AFS reserves the right to act as RFO for selected non-AJW-3 developed procedures.

SECTION 4. FACILITY UTILIZATION AND MONITORING

SECTION 4. FACILITY UTILIZATION AND MONITORING

208. FREQUENCY SERVICE VOLUMES. In establishing instrument flight procedures, consideration must be given to the type of navigation facilities available and to their limitations. a. All electronic navigation facilities are installed in accordance with frequency separation specified in distances and altitudes. Specific frequency protected service volumes are contained in Order 6050.32, Spectrum Management Regulations and Procedures Manual. The Regional Frequency Management Officer (FMO) primarily uses this order. The NFPO should maintain a copy of Order 6050.32 on file 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. 209. 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 FAA Form 6050-4, Expanded Service Volume Request, is mandatory. Flight check measurements must not be used as a substitute for an approved ESV [see figures 2-1, 2-2, and 2-3]. a. VOR/VORTAC/TACAN. Facility Usable Usable Class Height Above Distance Facility (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-1. Standard Class L/H

Service Volume.

100 NM (185 KM) 60,000 FT (18,288 M)

45,000 FT (13,716 M)

18,000 FT (5,486 M)

14,500 FT (4,420 M)

1,000 FT (305 M)

40 NM (74.1 KM)

130 NM (241 KM)

Figure 2-2. Standard Low Altitude

100 NM (185 KM) 60,000 FT (18,288 M)

Service Volume.

18,000 FT (5,486 M)

1,000 FT (305 M)

40 NM (74.1 KM)

Figure 2-3. Standard Terminal

Service Volume.

12,000 FT (3,658 M)

1,000 FT (305 M)

25 NM (46.3 KM)

b. NDB. Facility Distance Class (Miles) COMLO NOTE: Low frequency 15 MH beacons have no 25 H standard height 50 HH limitations 75 c. ILS. Height Above Distance Facility Facility (Miles) Localizer (FC) 4,500 and below 18 Localizer (BC) 4,500 and below 18 Glide Slope (2o-4o) varies with angle 10 d. MLS [see figures 2-4 and 2-5]. Height Above Distance Facility Facility (Miles) MLS (FC) 20,000 and below 20 MLS (Back AZ) 5,000 and below 20 MLS EL 20,000 and below 20 Figure 2-4. MLS Azimuth Coverage.

+40° -40°

-40° +40°

0°

20 NM

20 NM FAA

20 NM FAA

AZIMUTH

*BACK AZIMUTH

*WHEN INSTALLED

CENTERLINE

EXTENDED

Figure 2-5. MLS Elevation Coverage.

20,000 FT

TYPICAL GLIDE PATH

EL

20 NM

LOWER

LIMIT

15°

3°

0.9°

210. REQUESTS FOR EXPANDED SER- VICE VOLUMES (ESV). a. When ATC requires use of NAVAIDs above/below/beyond limitations cited in paragraphs 209a through 209d, ATC submits an ESV request, with a description of the flight procedure requiring it. This request is first reviewed by the Frequency Management Officer (FMO). 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 the NFPO. b. The National Flight Procedures Office 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 NFPO approval.

TYPICAL GLIDE PATH

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. The NFPO initiates a change action via the Spectrum Management web site (ESVMS) and explains the action required; e.g., "R-035 changed to R-038 due to variation change to 23E/05 effective 4 AUG 04." 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 Expanded Service Volume Management System via the FAA Intranet web site. 211. 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 course guidance must start and end at an approved navigational fix. b. The use of localizers for en route instrument flight procedures must be limited to those instances where it is essential to air traffic control. c. Appropriate navigational aids will be recommended at the earliest possible date in order to discontinue the use of the localizer for course guidance in the en route environment. 212. 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. Very high frequency omnidirectional radio range (VOR), very high frequency omnidirectional radio range collocated with tactical air navigation (VORTAC), and ILS facilities as well as new nondirectional beacons (NDBs) and marker beacons installed by the FAA, are provided with an internal monitoring feature. Older FAA NDBs and some nonfederal 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. (2) Category 2. Internal monitoring with status indicator at control point inoperative, but pilot reports indicates the facility is operating normally. (This is a temporary situation that requires no procedural action. (3) Category 3. Internal monitoring only. Status indicator is not installed at control point. (4) Category 4. Internal monitor not installed. Remote status indicator provided at control point. This category is applicable only to nondirectional beacons. 213. 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 procedures development. The Air Traffic Organization is responsible for issuing

NOTAMs on these out-of-service facilities when pilot reports indicate facility malfunction. c. Category 3 facilities may be used in accordance with the following limitations: (1) Alternate minimums must not be authorized if facility provides final approach course guidance; is required for procedure entry; is used to define the FAF; or is used to provide missed approach guidance. See also paragraph 853b. (2) When a facility is used to designate a stepdown fix, alternate minimums must be no lower than the circling minimums required without the stepdown fix. (3) Consider denying or adjusting terminal routes that require reception of succeeding Category 3 facilities to avoid obstacles. (4) Dogleg airways or routes must not be predicated on these facilities. (5) 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. 214. 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 (FAF). As a nonprecise 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 10.

SECTION 5. IMPLEMENTING EPOCH YEAR MAGNETIC VARIATION (MV)

SECTION 5. IMPLEMENTING EPOCH YEAR MAGNETIC VARIATION (MV)

215. 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. 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, determine the magnetic variation (MV). Changing values for MV are tabulated and published on a 5-year epoch basis; e.g., 85, 90, 95, 00, 05, etc. In order to assist in stabilizing the National Airspace System (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. b. Participating Offices. Management and control of Epoch Year MV values require action by the following offices: (1) National Aeronautical Charting Office (NACO). (2) Technical Operations Aviation System Standards (AJW-3). (3) National Flight Data Center (NFDC). (4) Western, Central, and Eastern Technical Operations. (5) Regional Airports Divisions. (6) Military Organizations.

216. RESPONSIBILITIES.

a. NACO. (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. b. Technical Operations Aviation System Standards. (1) 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 AJW-3 and the Regional Airports, Air Traffic, and the applicable Technical Operations Service Area offices with respect to matters pertaining to change in navigational aid or airport MV of Record and its effect on instrument flight procedures.

(2) Function as the focal point for 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 adjust-ment 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 navigational facilities (including military facilities) and airports in whole degree increments. MVs of record are available in the AVNIS facility database. 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 redesignation of radials are required. (5) Develop and maintain an official listing/record of navigational aids and airports by geographical location at the end of each Epoch Year to indicate the currently assigned MV of most recent Epoch Year's MV, 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 2 degrees or more between the MV of record and the nearest future Epoch Year value. (6) Notify NFDC (in AJR-32) 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. (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, obstacle departure procedures (ODPs), SIDs, STARs, and any other application to instrument flight procedures. Use the MV of record (or as officially changed) to develop instrument flight procedures - regardless of the MV shown on the chart being used. (8) 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 IAPs.

Modify all 14 CFR Part 95 Direct and Off-Airway (Non-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 ATC (ARTCC and approach control) in an attempt to eliminate routes, fixes, and instrument procedures that are no longer required. (9) Navigational aids NOT supporting en route structure: (a) Initiate implementation of the nearest future Epoch Year MV 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 857n and 857o]. (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 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 chapter 4, section 5. (10) Military Facilities. (a) Accomplish MV changes for U.S. Army facilities in the same manner as for civil facilities; however, obtain the installation commander's prior approval. (b) Notify the appropriate military representatives, in writing, when the need to change the MV of other military facilities is identified.

(11) Airports. (a) Amend IAPs, SIDs, and ODPs that specify runway designator numbers affected by MV change. (b) Notify the applicable Air Traffic Service Area Office of the need for amendment action if STARs contain runway designator numbers affected by MV change. (c) Take appropriate NOTAM action if repainting of an affected runway is not accomplished on the required date. c. NFDC. Upon notification by the NFPO of any change to MV of record, publish a notice of change in the NFDD to indicate the effective date of such change. d. Western (AJW-W), Central, (AJW-C), and Eastern (AJW-E) Technical Operations. Coordinate with the FPFO to obtain the MV of record for assignment to newly installed or relocated navigational aids. e. Regional Airports Division. Coordinate with the FPFO prior to establishing or revising runway designator numbers for an airport having one or more instrument approach or departure procedures, to determine the MV to be applied to the runway true bearing.

Determination of the runway designator number should be a matter of joint agreement with the NFPO, and be accomplished sufficiently in advance to allow for procedural amendments. f. Military Organizations. Contact the NFPO to obtain the MV of record to be applied to navigational aids or airports under military jurisdiction. Once obtained, it is the responsibility of the military to provide the NFDC (AJR-32) MV updates made to navaids and/or procedures. 217. 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 858e(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, paragraph 7d. 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 3 degrees or more, the MV of record must be changed to the nearest future Epoch Year value. When the difference is less than 3 degrees, AJW-3 must consider implementing the nearest future Epoch Year value when workload permits. 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. 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 bearing must be assigned the same MV as the airport.

Note: The actual runway bearing 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 using 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.

218.-219. RESERVED.

SECTION 6. NOTICES TO AIRMEN (NOTAMs)

SECTION 6. NOTICES TO AIRMEN (NOTAMs)

220. GENERAL. NOTAMs provide timely knowledge to airmen, and other aviation interests, of information or conditions that are essential to safety of flight. NOTAMs pertaining to instrument procedures remain in effect until the pertinent charts and publications are amended or the condition requiring the NOTAM ends. This section deals primarily with policy for issuing Flight Data Center (FDC) NOTAMs and NOTAM Ds when required to maintain the accuracy and currency of charted terminal and en route flight procedures. Also see Order 8260.3, United States Standard for Terminal Instrument Procedures (TERPS), paragraph 150e. 221. NATIONAL NOTICE TO AIRMEN SYSTEM. A National Notice to Airmen System has been established to provide airmen with the current status of the National Airspace System (NAS). This system is under the purview of FAA’s Air Traffic Organization, Vice President of System Operations (AJR-0). Management and operational guidance is contained in Order 7930.2, Notices to Airmen (NOTAMs).

The following is a brief summary of the different type NOTAMs and issues applicable to instrument procedure changes, NAVAID outages, and government chart corrections. a. FDC NOTAMs are issued through the U.S. NOTAM Office (USNOF) and primarily used to disseminate safety of flight information relating to regulatory material [see Order 7930.2, chapter 7, for specific FDC NOTAM categories]. FDC NOTAMs are numbered by the U.S. NOTAM System (USNS) to reflect the year of issuance and the sequence number for the calendar year, (e.g., 5/0445). FDC NOTAMs are transmitted on all Service B circuits, and stored in the Consolidated NOTAM System, after which they are entered in the Notices to Airmen Publication (NTAP) until canceled. The NTAP is distributed via U.S. mail and is available on-line at http://www.faa.gov/airports_airtraffic/air_traffic/p ublications/notices. b. FDC NOTAMs may be either temporary (T-NOTAMs) or permanent

(P-NOTAMs), as specified below, when used to promulgate changes to published instrument flight procedures, and corrections to U.S. Government charts. FDC NOTAMs must be prefixed with an action code as follows: (1) FI/T (Flight Information/ Temporary). Use this prefix when safety of flight issues requires changes to SIAPs, airways, or textual DPs. If the condition requiring the NOTAM will be effective for more than four charting cycles (224 days), an abbreviated or full amendment 8260-series form must be submitted to amend the procedure. The 8260-series form must be submitted as soon as possible to allow publication of the procedural change within the 224-day timeframe [see paragraph 813]. (2) FI/P (Flight Information/ Permanent). Use this prefix only to promulgate U.S. Government charting correction information. Cartographic agencies may initiate immediate changes to charted information based upon the P-NOTAM information. P-NOTAMs may NOT be used for changes to SIAPs, airways, takeoff minimums, ODPs, SIDs or STARs.

Refer to paragraphs 224b and 224c for graphic DP and STAR NOTAM procedures. c. NOTAM Ds are issued under the Flight Service Stations' Accountability System and receive the same dissemination as the surface weather report for the originating station. NOTAM Ds provide the user with current information on an hourly basis and are numbered to reflect the month of issuance and the sequence number within the month, (e.g., 06/018). 222. FDC T-NOTAM PREPARATION, REVIEW, AND TRANSMITTAL. a. The NFPO is the primary office responsible for formulating procedural and airway FDC T-NOTAMs and forwarding them for transmittal. The NFPO is also the office of primary responsibility for developing specific internal guidance for T-NOTAM preparation, quality control, transmittal, cancellation, and follow-up actions. This guidance must be developed in concert with the NFDC, the NACO Requirements and Technology Staff (R&T), and the U.S. NOTAM Office (USNOF). AFS-420 must be provided the opportunity to review and

comment on the procedures prior to implementation. As a minimum, the following items must be included in the guidance: (1) Procedures to ensure that all FDC T-NOTAMs are coordinated with the affected ARTCC facility at the time of submission, or if unable, during the next normal workday [see Order 8260.3, Volume 1, paragraph 150]. The NFPO/FPFO must also attempt to notify the airport manager at the affected location whenever possible.

Note: ARTCCs are responsible for forwarding FDC NOTAM information to the affected terminal facilities under Order 7930.2, paragraph 2-2-3. (2) Procedures to ensure ALL FDC T-NOTAMs are reviewed for accuracy, completeness, content, etc. prior to submission. (3) Procedures to ensure the NFDC is provided an information copy of all Instrument Flight Procedures (IFP) T-NOTAMs and cancellations to ensure that the NTAP is properly maintained. (4) Procedures to ensure the USNOF notify the submitting agency and the NFDC of all changes in instrument procedure FDC NOTAM numbering. (5) Procedures to ensure all FPFO or Flight Inspection Operations Group (FIOG) initiated FDC NOTAMs and NOTAM Ds are coordinated through the NFPO.

b. The NFPO must review amended SIAP charts, take-off minimums, textual ODPs, and en route charts to ensure procedural changes are charted correctly and cancel NFPO initiated FDC T-NOTAMs on the effective date of the amended procedure(s). c. The NFDC will review applicable FDC NOTAMs for accuracy, format, completeness, and database agreement. Discrepancies noted by NFDC will be forwarded to the originating NFPO branch for resolution. NFDC is also responsible for compiling NOTAMs for inclusion in the NTAP. d. The USNOF is responsible for ensuring that FDC NOTAMs are in the proper format under this directive and Order 7930.2.

Questions/discrepancies will be addressed to the submitting agency or the NFPO as appropriate. The USNOF must ensure that NFDC and the FDC NOTAM originating office are appraised of all changes in instrument procedure related FDC NOTAM numbers; e.g., when a NOTAM is canceled and reissued due to typographical error, etc. The NACO Requirements and Technology Team must be notified if changes are made to P-NOTAMs correcting U.S. Government charts. The FDC NOTAMs affecting FAA developed military SIAPs at civil locations must be issued separately and forwarded to the USNOF military representative. 223. FDC P-NOTAM PREPARATION, REVIEW, AND TRANSMITTAL. a. The NACO Requirements and Technology (R&T) Team is the primary office responsible for formulating FDC P-NOTAMs used to correct chart printing and compilation errors related to all U.S. Government aeronautical charting products and forwarding them for transmittal. b.

When a printing or compilation error is noted on a U.S. Government aeronautical charting product; e.g., the Terminal Procedures Publication (TPP), NACO, NFPO, NFDC, and the FAA Cartographic Standards Branch will jointly determine if the error can be safely addressed by NOTAM or whether the instrument flight procedure must be suspended pending issuance of a replacement chart. AFS-420 will provide operational/criteria input as required. c. The NACO R&T Team is also the office of primary responsibility for developing specific internal guidance for P- NOTAM preparation, quality control, transmittal, cancellation, and follow-up actions. This guidance must be developed in concert with the NFDC, the NFPO, and the USNOF. AFS-420 must be provided the opportunity to review and comment on the procedures prior to implementation. As a minimum, the following items must be included in the guidance: (1) Procedures to ensure that all FDC P-NOTAMs are coordinated with the affected ARTCC facility at the time of submission, or if unable, during the next normal workday.

The NACO must also attempt to notify

the airport manager at the affected location, whenever possible. (2) Procedures to ensure that ALL FDC P-NOTAMs are reviewed for accuracy, completeness, content, etc. prior to submission. (3) Procedures to ensure that the USNOF notifies the NACO Requirements and Technology Team and the NFDC of all changes in chart correction FDC P-NOTAM numbering; e.g., when a NOTAM is canceled and re-issued by the USNOF. (4) Procedures to ensure the NFDC is provided an information copy of all chart correction P-NOTAMs and cancellations to ensure that the NTAP is properly maintained. 224. INSTRUMENT APPROACH and TEXTUAL DEPARTURE PROCEDURE NOTAMs. A complete review and a new amendment are the preferred methodology for permanent procedure changes, particularly when applying new or revised TERPS criteria.

However, it is recognized that this may not always be possible due to time constraints workload, staffing level, etc. An FDC T-NOTAM followed by an abbreviated 8260-series form within the allotted 224 days is an equally effective means of updating SIAP charts and textual DPs within the following guidelines: a. Whenever the need for a NOTAM to a procedure arises, AJW-32 must review the procedure and ascertain that there is no other safety of flight changes required. Do NOT prepare a NOTAM solely to address minor nonsafety related discrepancies to a SIAP. b. Procedural minimums must not be lowered by NOTAM except as allowed by Order 8260.3, Volume 1, paragraph 150e. c. Exercise caution in initiating or adding a NOTAM to a procedure when there is already a current NOTAM in effect for the procedure. In many cases close follow-up action, including canceling and reissuing NOTAMs, will be necessary to ensure there is no confusion for pilots and chart producers. All FDC NOTAMs must be issued against the currently published procedure.

Example:

The currently published SIAP is AMDT 3 and AMDT 3A has been forwarded but not yet published. Another T-NOTAM is required prior to AMDT 3A. Issue a T-NOTAM against AMDT 3. When AMDT 3A is published, the T-NOTAM must be canceled and reissued for AMDT 3A. d. When changes to civil procedures also affect FAA-developed military procedures at civil or joint-use airfields, the NFPO must issue a separate FDC or military-series NOTAM for the military procedure as specified in Orders 8260.15, United States Army Terminal Instrument Procedures Service, and 8260.32, United States Air Force Terminal Instrument Procedures Service. The NFPO must request the USNOF to forward the civil NOTAM and the reason to the cognizant military authority for appropriate military NOTAM action. e. NOTAM requirements for FAA developed U.S. Army procedures must be processed under Order 8260.15. NOTAM requirements for FAA developed U.S. Air Force procedures at civil airfields must be processed under Order 8260.32. 225. GRAPHIC ODP, SID, and STAR NOTAM PREPARATION, REVIEW, AND TRANSMITTAL. a.

Changes to graphic ODPs and SIDs must be promulgated as NOTAM Ds under Order 7930.2. The NFPO is responsible for formulating NOTAM Ds for graphic ODPs and SIDs and forwarding them for transmittal by the USNOF. These NOTAMs are issued by the USNOF using the accountability code “USD. The following format examples are provided: USD 12/001 SAN BORDER THREE DEPARTURE JULIAN TRANSITION: FROM OVER BROWS INT VIA JLI R-182 TO JLI VORTAC USD XX/XXX LAX CHATY TWO DEPARTURE, GORMAN TRANSITION: MINIMUM ALTITUDE BROWS, INT TO GMN VORTAC, 8,000 FT In the first example above, “USD” is the NOTAM accountability code; “12/001” is the NOTAM number which is assigned by the USNOF (first

NOTAM (D) issued in December); “SAN” indicates the three-letter airport identifier; the remainder is the NOTAM text. b. Changes to STARs requiring NOTAM action are also promulgated as NOTAM Ds. The appropriate ARTCC is responsible under Order 7930.2 for initiating, tracking, and canceling STAR NOTAMs. c. The NFPO is the office of primary responsibility for developing specific internal guidance for DP NOTAM D preparation, quality control, transmittal, cancellation, and follow-up actions. This guidance must be developed in concert with the NFDC, NACO R&T Team, and the USNOF. AFS-420 must be provided the opportunity to review and comment on the procedures prior to implementation. The following items must be included in the guidance: (1) Procedures to ensure that ALL NOTAM Ds are reviewed for accuracy, completeness, content, etc. prior to submission. (2) For SIDs serving multiple airports, a separate NOTAM D must be prepared for each airport affected by the SID.

(3) Temporary and permanent conditions may be promulgated via the NOTAM D process; however, NOTAM Ds must not be used as a source to effect charting changes. Permanent procedural changes to graphic DPs must be made via a new or amended 8260-15 series form within 224 days of the issuance of the associated NOTAM D. (4) The USNOF must review each NOTAM D to ensure formatting, contractions, etc. are correct and assign the NOTAM number. Questionable items must be resolved with the originator prior to issuance. (5) Once issued, the NFPO is responsible for obtaining the NOTAM D number from the USNOF, tracking, and canceling the NOTAM when the condition requiring the NOTAM is no longer applicable. 226. GENERAL NOTAM D ACTIONS. a. When a NOTAM D is issued closing an airport permanently, an FDC NOTAM need

not be issued denying use of a SIAP. A routine procedure cancellation should be processed. b. When a NOTAM D is issued to shut down a facility permanently, only routine cancellations of procedures predicated on that facility are required. FDC NOTAMs may be required for other procedures supported by the affected facility. c. When a NOTAM D is issued closing a runway, an FDC NOTAM need not be issued denying straight-in minimums to that runway. If the closing is permanent, routine procedure cancellations, including takeoff/departure procedures, must be processed immediately. d. When a NOTAM D is issued for a facility shutdown or outage, an FDC NOTAM denying SIAP use is not required for those SIAPs using only that facility. However, other SIAPs in the vicinity must be reviewed to determine if that facility supports courses or fixes; in such cases, those SIAPs require an FDC NOTAM. Particular attention must be given to fixes supporting stepdown minimums and missed approach procedures, which are predicated on the out-of-service facility.

It is not necessary to issue NOTAMs for fixes and terminal route segments which are related to unusable airway segments from the subject facility. Do not issue “Radar Required” NOTAMs on unusable or restricted airway segments [see paragraph 463]. e. Area Navigation (RNAV) Substitution. Aircraft equipped with RNAV systems may substitute them for inoperative ground NAVAIDs. However, RNAV systems must not be substituted for NAVAIDS providing final approach course guidance on instrument approach procedures. (1) When the use of an instrument approach procedure, departure procedure (SID or ODP), or standard terminal arrival (STAR) is restricted or prohibited by NOTAM because of a NAVAID (VOR, NDB, compass locator, or DME) outage, the NOTAM does not apply to aircraft equipped with suitable GPS RNAV systems. For clarification, state the reason for the restriction in the text of the procedural NOTAM D or FDC NOTAM.

Examples: A DME antenna is out of service: "DME MINIMUMS NA EXCEPT FOR AIRCRAFT EQUIPPED WITH SUITABLE RNAV SYSTEM WITH GPS, ORD DME OTS." An LOM used for procedure entry and/or missed approach clearance limit for an ILS approach is out of service: "PROCEDURE NA EXCEPT FOR AIRCRAFT EQUIPPED WITH SUITABLE RNAV SYSTEM WITH GPS, GR LOM OTS." A VOR is used in a departure procedure (ODP or SID) is out of service: "GEYSER THREE DEPARTURE NA EXCEPT FOR AIRCRAFT EQUIPPED WITH SUITABLE RNAV SYSTEM WITH GPS, JAC VOR OTS." (2) In certain circumstances, AFS-400 may determine that the use of RNAV systems that utilize DME/DME/IRU inputs should be allowed. In these instances, insert the phrase "OR DME/DME/IRU" after "SUITABLE RNAV SYSTEM WITH GPS." Include any required DME facilities to support DME/DME/IRU operations.

Example: "HOOVER THREE DEPARTURE NA EXCEPT FOR AIRCRAFT EQUIPPED WITH SUITABLE RNAV SYSTEM WITH GPS OR DME/DME/IRU, PGS VOR OTS. BLD AND DRK MUST BE OPERATIONAL FOR DME/DME/IRU ON PEACH SPRINGS TRANSITION. DRAKE TRANSITION NA FOR DME/DME/IRU." f. When a NOTAM D removes a localizer from service, the SIAP is unusable. If the GS is out, the precision approach is unusable. If other ILS components are out, the inoperative table applies. g. When radio control of approach lights or runway lights are commissioned or the frequency is changed, Flight Inspection issues a NOTAM D in accordance with Order 8200.1, United States Standard Flight Inspection Manual. h. When Airways Facilities issues a NOTAM suspending Category II/III minimums, the NFPO will then amend procedures as required.

227. AIRWAY NOTAMs. When a restriction or a change to an airway requires a NOTAM, NFPO must prepare and forward an FDC T-NOTAM following the procedures in paragraph 223. a. NOTAMs, reflecting airway changes within one or more ARTCC’s airspace, are issued under the affected ARTCC identifier as Center Area NOTAM (CAN) FDC NOTAMs on the NOTAM circuit. The formats specified in Order 7930.2, chapter 7, section 1 must be followed regarding the number of ARTCCs and states affected. b. Airway changes involving a single state and one or more ARTCCs must be issued with the ARTCC identifier followed by the twoletter state code. The two-letter state code must also follow all NAVAID and fix designators. Examples: "FDC 7/0001 ZFW OK FI/T AIRWAY ZFW ZKC. V140 SAYRE (SYO) VORTAC, OK TO TULSA (TUL) VORTAC, OK MEA 4,300. FDC 7/0002 ZKC OK FI/T AIRWAY ZFW ZKC. 140 SAYRE (SYO) VORTAC, OK TO TULSA (TUL) VORTAC, OK MEA 4,300. REASON: TEMPORARY NEW TOWER. OE 07-ASW-0123." c. If the airway NOTAM affects one but less than four ARTCCs and multiple states, issue one NOTAM for each affected ARTCC. If the NOTAM affects four or more ARTCCs, send one NOTAM using "FDC” as the facility identifier. d. If the restriction will exceed the time limit established in paragraph 222b, forward an updated Form 8260-16 and/or 8260-2 simultaneously to NFDC and NACO for charting. 228. FDC NOTAMs FOR SPECIAL INSTRUMENT APPROACH PROCEDURES (SPECIALS). FDC T-NOTAMs may also be used to promulgate safety of flight information relating to

Specials provided the location has a valid landing area identifier and is serviced by the U.S. NOTAM system. The AJW-3 NOTAM Entry System (NES) will provide immediate feedback as to whether the location is included in the NOTAM system. There are four possible considerations to determine FDC NOTAM action for Specials. a. If the Special is maintained by the NFPO and the location is in the U.S. NOTAM system, then procedures for NOTAM processing by the NFPO will be similar to the procedures used for public, part 97 instrument approach procedures. Additionally, when preparing the NOTAM for submission, include the word "SPECIAL" in parenthesis immediately following the city/state and prior to the procedure title [see paragraph 229 for an example]. The NFPO will notify the RFSD-AWOPM as soon as practicable. b. If the Special is not maintained by the NFPO but the location is in the U.S. NOTAM system, then the organization responsible for maintaining the procedure will notify the applicable RFSD-AWOPM of the change/ outage. The RFSD-AWOPM will contact the NFPO with the appropriate information, who will take appropriate NOTAM action. If the RFSD- AWOPM cannot be immediately contacted and the condition is critical to flight safety, the Regional FPFO or the NFPO will be contacted directly and provided adequate information to initiate immediate NOTAM action. The NFPO will notify the RFSD-AWOPM as soon as practicable.

Note: After duty hours, contact the stand-by NFPO representative at (405) 954-8260.

c. If the Special is maintained by the NFPO and the location is not in the U.S. NOTAM system, then the NFPO will notify the applicable RFSD-AWOPM of the change/ outage. The RFSD-AWOPM must contact the user(s) of the procedure to disseminate appropriate action (e.g., NA the procedure, raise applicable minimums, etc.). d. If the Special is not maintained by the NFPO and the location is not in the U.S. NOTAM system, then the organization responsible for maintaining the procedure will notify the applicable RFSD-AWOPM of the change/outage. The RFSD-AWOPM must

contact the user(s) of the procedure to disseminate appropriate action (e.g., NA the procedure, raise applicable minimums, etc.). 229. NOTAM CONTENT. a. FDC SIAP NOTAMs must identify the procedure being amended and the current amendment number. The NOTAM must be as concise as possible, and must NOT contain information that could be published at a later date by a routine amendment. For example, changes to the touchdown zone or airport elevation, which does not affect visibility minimums, do not require NOTAM action. b. The text must be prepared by the NFPO using plain language and those contractions found in the NTAP. Specialists must keep in mind that the NOTAM is directed to the pilot, and should be worded so that the intended change will not be misinterpreted. Avoid the use of internal cartographic instructions that have no meaning to pilots. Spell out NAVAID names in clear text followed by the identifier. If it appears that the NOTAM length will exceed 20 lines, refer to Order 7930.2, paragraph 4-3-4. c.

For temporary obstructions, include the type, elevation, distance, and direction from the airport or runway threshold, as appropriate, as the last line of the text. d. Include a reason for the NOTAM following the NOTAM text. This information will not be transmitted as a part of the NOTAM text, but will inform the NFDC and the USNOF of the basis for the NOTAM. It will also ensure the data is retained in the NOTAM historical files. Example: FDC 7/ … ORD FI/T CHICAGO O'HARE INTL, CHICAGO, IL. VOR RWY 22R AMDT 8B... MDA 1400/HAT 750, VIS 1-1/2 ALL CATS. TEMPORARY CRANE 1100 MSL 1.2 NM SE OF RWY 23. (Specify distances less than 1 NM in feet. REASON: TEMPORARY CRANE FOR 90 DAYS. OE 06-AGL-2689 FDC 7/GPT FI/T GULFPORT-BILOXI INTL, GULFPORT, MS.

VOR RWY 31 AMDT 18... S-31 MDA 720/HAT 693 ALL CATS. VIS CAT C 2, CAT D 2-1/2. CIRCLING MDA 720/HAA 692 ALL CATS. VIS CAT C 2, CAT D 2-1/2. RADAR 1 AMDT 3… VOR/DME OR TACAN RWY 31 ORIG. S-31 MDA 660/HAT 633 ALL CATS. VIS CAT C 1-3/4, CAT D 2, CAT E 2-1/4. CIRCLING CATS A/B MDA 660/HAA 632. TEMPORARY CRANE 410 MSL 1.5 NM SE OF RWY 31. REASON: TEMPORARY CRANE FOR 160 DAYS. OE 07-ASO-0101 FDC 7/ … LAN FI/T CAPITAL CITY, LANSING, MI. ILS RWY 10R AMDT 8A... ILS RWY 28L AMDT 24... VOR RWY 6 AMDT 23B... VOR RWY 24 AMDT 7E... CIRCLING MDA 1420/HAA 559 ALL CATS. REASON: NEW BUILDING, 1115 MSL. OE 07- AGL-0123 Note: Since the above condition is permanent, SIAP Amendments must be processed within 224 days. “FDC 7/ PAJN FI/T JUNEAU INTERNATIONAL, JUNEAU, AK (SPECIAL) LDA-2 RWY 8 AMDT 9… PROCEDURE TURN NA.

REASON: PROCEDURE TURN (PT) STEP- DOWN FIX GREATER THAN 4 NM FROM PT FIX. FDC 7/ … AXH FI/T HOUSTON- SOUTHWEST, HOUSTON, TX. NDB RWY 28 AMDT 4... LOC/DME RWY 10 AMDT 2A...CHANGE ALL REFERENCE TO RWY 10-28 TO RWY 9-27.” REASON: RUNWAYS RENUMBERED FOR MAGNETIC VARIATION CHANGE. FDC 5/ FI/P CORRECT U.S. GOVERNMENT CHART NORTH ATLANTIC ROUTE CHART, EFFECTIVE 17 MAR 2005… CORRECT ROUTE IDENTIFIER A763 BETWEEN GRAND TURK ISLAND (GTK) VORTAC AND AGUADILLA (BQN) VORTAC TO R763. FDC 5/ FI/P CORRECT U.S. GOVERNMENT IFR EN ROUTE LOW ALTITUDE CHART L-3, PANEL C, EFFECTIVE 18 JAN 2007... VICTOR AIRWAY V458 BTW JLI VORTAC (N 33 08 25.651/W116 35 09.365) AND KUMBA INT (N32 45 43.180/W116.03 13.370) MEA SHOULD READ 7700. FDC 7/ 7D2 FI/P OAKLAND/TROY, TROY, MI. VOR OR GPS-A, AMDT 3... CORRECT FAF TO READ PERLS INT. VS PERSL INT.

SECTION 7. QUALITY/STANDARDIZATION OF

SECTION 7. QUALITY/STANDARDIZATION OF

INSTRUMENT FLIGHT PROCEDURES

230. NFPO ACTION. a. The NFPO is responsible for the accuracy of instrument flight procedures it develops, and for establishing and conducting a system of quality control that ensures such procedures conform to applicable criteria, standards, and policy. b. The NFPO’s system of quality control must ensure that all flight procedures and NOTAMs submitted to NFDC are of a professional quality that will not require corrections or changes following release. c. When unusual circumstances exist, for which policy is not clear or is nonexistent, request a policy determination from AFS-460 PRIOR TO submission for publication. AFS-460 will issue appropriate instructions as necessary. d. Instrument charts produced by the National Aeronautical Charting Office (NACO) will be reviewed by the NFPO, upon receipt, for

INSTRUMENT FLIGHT PROCEDURES

variations from information submitted for publication and for clarity of the graphic portrayal. Charting errors detected must be forwarded directly to NACO R&T for corrective action under paragraph 224b. Charts that do not clearly portray the procedure(s) as designed should be referred to AFS-460 and the NACO, with recommendations for charting improvements. 231. AFS-460 ACTION. a. AFS-460 is responsible for providing oversight of the NFPO Quality Assurance (QA) process to determine conformance with applicable criteria, standards, and policy. b. Preliminary reviews may be conducted by AFS-460 upon request by the NFPO. When unusual circumstances exist, AFS-460 will issue appropriate instructions to the NFPO as necessary. 232.-239. RESERVED.

SECTION 8. PERIODIC REVIEW OF INSTRUMENT FLIGHT PROCEDURES

SECTION 8. PERIODIC REVIEW OF INSTRUMENT FLIGHT PROCEDURES

240. GENERAL. a. This section prescribes the minimum frequency of review of instrument procedures. When deemed necessary, and in the interest of safety or for other proper justification, make more frequent reviews. Review all instrument procedures to ensure that requirements for obstacle clearance, navigational guidance, safety, and practicality are met. Immediately comply with changes to criteria that relate to safety of flight. Use the review to ensure compliance with all other changes to criteria. FPFOs can normally present current reviews of OEs, F&E, and AIP projects pertinent to the review process. b. A review is considered complete if it occurs in the period from one month prior to one month after the month in which the review is due; e.g., if the review is due in July, the window is June 1 to August 31. If the window is met, the procedure review due month remains unchanged. However, if the review occurs outside of the specified window, the next review is due in the month in which the review was actually completed. c.

When facility restrictions are established or changed, review all associated flight procedures. Take particular care to evaluate unpublished procedures such as off-airway, direct, and substitute routes. 241. NFPO ACTION. a. SIAPs, SIDs, ODPs, and STARs. (1) Review at least once every two years. (2) Review all feeder, initial, intermediate, final, circling, missed approach, and departure procedure areas for any changes that would affect flight altitudes. To avoid proliferation of conflicting data on IFPs at an airport, the periodic review should include all procedures at that airport [see paragraph 811a]. (3) Ensure that all procedures are contained within controlled airspace as prescribed in chapter 5.

(4) Ensure that minimums meet criteria. Review IFP forms for conformance to current standards. Check published IFP charts and text for correct portrayal. (5) Verify current magnetic variation values. (6) Verify continued need for IFPs based on usage rate, economic need, etc. Cancel IFPs that are no longer required. (7) Verify the validity of existing waivers. Cancel waivers no longer required. (8) Coordinate proposed IFP changes (including FDC NOTAMs) in advance with the applicable FPFO, airport management, and servicing air traffic control facility when application of new or revised criteria raises minimum procedure altitudes and/or increases landing minimums. b. Airways, Airway Segments, and Routes. (1) Review at least once every 4 years. (2) Verify controlling obstacles and assure that authorized altitudes meet obstacle clearance requirements. Use current en route charts as airway checklists. (3) Verify continued need for off-airway and Part 95 direct routes. Cancel routes that are no longer required. c. Fixes. (1) Review all fixes in conjunction with the associated IFPs, airways, or routes [see section 10]. Assure that Form 8260-2 entries for facility type, class, radial/course/bearing, distances, least divergence angle, and charting requirements are correct. Verify holding requirements and controlling obstructions. (2) Cancel fixes and holding which are no longer needed.

d. All Procedures.

(1) Establish and maintain a system of control to assure that reviews are accomplished. (2) Take remedial action by NOTAM or revised 8260-series form. (3) Review all associated waivers in conjunction with any procedure review.

(4) Annotate and incorporate editorial changes noted during the review in the next revision. Do NOT make IFP amendments solely to correct an MSA altitude except when the MSA provides less than 950 ft of obstacle clearance. 242.-249. RESERVED.

SECTION 9. COMMUNICATIONS AND WEATHER

SECTION 9. COMMUNICATIONS AND WEATHER

250. COMMUNICATIONS REQUIREMENTS. Order 8200.1, U.S. Standard Flight Inspection Manual, chapter 8, defines communication tolerances and flight inspection procedures. Even though gaps in navigation course guidance may be approved, reliable communications coverage over the entire airway or route segment at minimum en route IFR altitudes must be available. a. MEAs or MAAs are predicated upon continuous approved communications capability for the entire designated segment. All available resources must be explored before restricting the use of altitudes of an airway or route due to a lack of acceptable communications coverage. Coordination must be effected with ATC for determination of the acceptability of communications coverage in a particular area. b. Mandatory communications with the appropriate ARTCC are not required; communications with other ATC facilities are allowable. Where necessary, in order to provide direct communications with a center, appropriate recommendations for a peripheral site should be made. c. Communications requirements for non-14 CFR Part 95 routes certified for a particular air carrier are the responsibility of appropriate FSDO operations inspector. 251. USE OF UNICOM. UNICOM may be used to satisfy the communications requirements of Order 8260.3, Volume 1, paragraph 122e; however, there are limitations on its use that must be considered. According to FCC Rules and Regulations, Part 87, Subpart C, UNICOM stations are not

authorized for ATC purposes other than the relay of the following information between the pilot and controller: a. Revision of proposed departure time. b. Time of takeoff, arrival, or flight plan cancellation. c. ATC clearances, PROVIDED a Letter of Agreement is consummated by the licensee of the advisory station (UNICOM) with the FAA. d. Weather information - only if there is no FAA control tower or Flight Service Station, or during periods when an FAA unit is not in operation. Direct transmission of approved altimeter setting to the pilot is authorized provided the procedure states an alternate course of action if UNICOM is not contacted.

Note: FCC regulation places the responsibility for the Letter of Agreement on the licensee, but FAA Handbook 7210.3 suggests that an ATC facility prepare the agreement. A communication capability between the UNICOM station and ATC is necessary to meet requirements of Order 8260.3, Volume 1, paragraph 122e. 252. AUTOMATIC ALTIMETER SETTING AND WEATHER REPORTING SYSTEMS. Approved devices for automatically reporting altimeter settings and weather may be used to satisfy the requirements of Order 8260.3, Volume 1, paragraph 122d. Special notes will be required on the approach charts. Examples of standard notes can be found in paragraph 855f. 253.-259. RESERVED.

SECTION 10. NAVIGATIONAL FIXES

SECTION 10. NAVIGATIONAL FIXES

260. GENERAL. Criteria for navigational fixes are contained in Order 8260.3, Volume 1, chapters 2 and 17. When using a VORTAC or VOR/DME, fixes should be defined by DME from the facility providing course guidance in addition to radials or course intersections. 261. REPORTING POINTS. Reporting points are established for use by the Air Traffic Organization (ATO) in the movement and separation of aircraft. Reporting points are divided into two categories, which are: a. Compulsory reporting points are designated by regulation and, therefore, require rule-making action. It is the ATO's responsibility to initiate airspace rule making action for the designation of compulsory reporting points. Unless the reporting point can be identified at the lowest operational altitude, it must not be designated a compulsory reporting point. b. Non-Compulsory reporting points may be established by the ATO without the requirement for rule making action. 262. UNPLANNED HOLDING AT DESIG- NATED REPORTING POINTS. a.

Where required for aircraft separation, ATO may request aircraft to hold at any designated reporting point in a standard holding pattern at the MEA or MRA, whichever altitude is the higher, at locations where a minimum holding altitude has not been requested. For this reason, the conditions to be considered for holding (obstacle clearance, communications, and facility performance) must be reviewed whenever reporting points are established or revised, even though specific holding authorization has not been requested by the ATC facility. b. Unplanned holding at en route fixes may be expected on airway or route radials, bearings, or courses. If the fix is a facility, unplanned holding could be on any radial or bearing. Where standard holding cannot be accomplished at the MEA or MRA, any necessary

limitations must be clearly indicated on Form 8260-2, Radio Fix and Holding Data Record. 263. REQUESTS FOR NAVIGATIONAL FIXES. a. Form 8260-2 is the vehicle used to transmit requests for the establishment, revision, or cancellation of navigational fixes, holding patterns, and/or reporting points. All fix requests must be processed through the NFPO. The NFPO may initiate Form 8260-2 for those navigational fixes that are required for the development of IFPs. Other operationally required navigational fixes must be coordinated with the appropriate ATC facility [see chapter 8, section 6]. b. Every effort should be made to use established fixes or NAVAIDs wherever possible in lieu of creating new fixes. Additionally, do NOT create a new waypoint over an existing fix or NAVAID. 264. NAMING NAVIGATIONAL FIXES. In order to satisfy the requirements of the Flight Management System (FMS), the following applies for all procedures: a. All navigational fixes must be named. Exceptions: Fixes used for navigation not to be named include Visual Descent Points (VDPs), radar fixes used on ASR and/or PAR procedures, RNAV missed approach point at threshold, and an ATD fix located between the MAP and the landing area marking the visual segment descent point on COPTER RNAV PinS approach annotated "PROCEED VISUALLY." Except as noted below, each name must consist of a 5-letter pronounceable word. Obtain 5-letter names from NFDC. Name fixes collocated with a facility (named in accordance with Order 7400.2, Procedures for Handling Airspace Matters, chapter 3) retains the same name as the facility. Navigational fixes to be named include: (1) Intersections defined by radials and/or bearings.

(2) DME and Along-Track Distance (ATD) fixes. (3) Stepdown fixes, regardless of segment in which located. Stepdown fixes between the FAF and MAP may be nonpronounceable 5-letter names. (4) Missed Approach Points (MAP) not located at the threshold of the landing runway. This may be a non-pronounceable 5-letter name. For non-RNAV procedures, if DME is available, it should be a DME fix. If DME or other ground-based NAVAID solution is not available, define the MAP with a Computer Navigation Fix (CNF).

Note: If a CNF is used to define the MAP on a non-RNAV procedure, FAF to MAP timing is required. (5) Starting and ending points of arcs. (6) Points where feeder or initial routes intercept the final approach course extended prior to the initial or intermediate fix. This includes cases where the intercept is via a heading. These are developed as computer navigation fixes. (7) RNAV Waypoints. (8) Computer Navigation Fixes (CNFs). These are non-pronounceable 5-letter fix names used to aid in computer navigation and are not used in ATC communications. (9) Fictitious Threshold Point (FTP). This is a CNF. (10) VFR Waypoints. These are nonpronounceable 5-letter names beginning with "VP." Example: VPXYZ (11) PFAF not collocated with a FAF that is separated by 1 NM or greater shall be a pronounceable, 5-letter name. Newly established PFAFs separated from the FAF of the underlying non-vertically guided procedure by less than 1 NM, must be named but can be treated as a CNF [see paragraph 264a(8)].

Note: Determination as to which fix, PFAF or FAF, should be given a pronounceable fix name or a non-pronounceable fix name should be determined in coordination between the procedure designer and the Air Traffic Control facility providing radar services. b. Coordinate with NFDC and the appropriate ARTCC when a fix name change is required. Document the change on Form 8260-2. c. When a fix is moved, the name must be changed if the fix is moved 5 NM or more unless operational requirements dictate otherwise. 265. DOCUMENTING NAVIGATIONAL FIXES. a. All named civil and military fixes must be documented and approved on Form 8260-2. Chapter 8 of this order contains instructions for entering data and submitting Form 8260-2. b. Military fixes are also maintained in the National Database and are used to support the air traffic system. Therefore, the requirement to document and flight inspect military fixes must receive the same priority as the fixes that support civil procedures. 266. CORRELATION OF NAVIGATIONAL FIXES AND CHANGEOVER POINTS (COPs). The designation of navigational fixes should be directly related to COPs. Care should be taken to avoid designating navigational fixes that require the use of a facility beyond the COP. Figure 2-6 is an example of the proper and the improper method of designating a navigational fix in relation to COPs.

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

267. MINIMUM RECEPTION ALTITUDES (MRA). At certain navigational fixes, VOR reception from an off-course facility may not be adequate at the lowest MEA associated with the route segment. In such cases when the MRA at the fix is higher than the MEA for instrument flight, the MRA must be established for the fix and indicated on Forms 8260-2 and 8260-16. Once established, an MRA will not be revised unless the reception altitude is changed by 200 ft or more [see paragraph 841f(3)(j)].

Figure 2-6. Proper and Improper Method of

Designating a Navigational Fix.

40

VOR “A”

VOR “C”

VOR “B”

INTERSECTION AND COP DESIGNATIONS ARE COMPATIBLE.

NO PROBLEM IN THIS CASE.

60

40

VOR “A”

VOR “C”

VOR “B”

COP AND INTERSECTION DESIGNATION ARE IN CONFLICT. IF INTERSECTION IS DESIGNATED OFF VOR’S B&C, COP WILL PREVENT USE OF VOR B AT THE INTER- SECTION.

REDESIGNATE INTERSECTION OFF VOR’S A&C. SOLUTION:

60

268. FLIGHT INSPECTION. After completion of required coordination, flight inspection personnel must confirm facility performance at the proposed operational altitudes. Where possible, determinations must be predicated on current facility performance records; otherwise, a flight check must be accomplished. 269. MAXIMUM AUTHORIZED ALTITUDES (MAA). MAAs are procedural limits that might be determined by technical limitations or such other factors as limited airspace or compatibility with other procedures. Where MAAs are required in connection with the publication of flight procedures, they are included on Forms 8260-2 and 8260-16, or worksheets used to process the data [see also paragraph 841d(2)(e)].

SECTION 11. OBSTACLE DATA 270. GENERAL. The primary purpose of obstacle evaluation is to determine how an object will impact instrument flight procedures. The evaluations provide accurate, consistent, and meaningful results and determinations only if procedure specialists apply the same rules, criteria, and processes during development, review, and revision phases. This section also provides basic information regarding obstacle data sources; establishes the minimum accuracy standards for obstacle data and its application in the development, review, or revision of instrument procedures; and provides information on the application of the minimum accuracy standards. The minimum standards, regardless of the data source, are to be applied by instrument procedure specialists in all instrument procedure obstacle evaluations. 271. OBSTACLE DATA SOURCES. a. The NACO maintains a Digital Obstacle File (DOF) that includes a record of all manmade obstructions reported under Part 77.

Continue reading ↓ 120 of 628 passages shown