Order 8260.19C Flight Procedures and Airspace
This document is cancelled. It may have been replaced. Check the official source before relying on it.
Text read by OCR from a scanned file. Check the original, as some words may be misread.
ORDER 8260.19C
ORDER 8260.19C
Flight Procedures and Airspace
September 16, 1993
U.S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION
Distribution: ZVN-826 Initiated By: AVN-220
9/16/93 8260.19C
FOREWORD
This order provides guidance for all personnel in the administration of the Flight Procedures and Airspace Program.
U.S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION
It defines responsibilities, establishes criteria, and provides standards to assure effective and orderly processing of all types of procedures actions.
Procedures personnel must use sound judgement, imagination, and initiative in carrying out their assigned responsibilities and duties. They are encouraged to recommend improved methods of operation.
Witliam H. Williams, Jr. Director of Aviation SystemStandards
Page i (and ii)
TABLE OF CONTENTS
TABLE OF CONTENTS
CHAPTER 1. ADMINISTRATIVE
SECTION 1. GENERAL
100. PURPOSE. 101. DISTRIBUTION 102. CANCELLATION.. 103. EXPLANATION OF CHANGES 104. FORMS.. 105. TERMS AND DEFINITIONS... 106. INFORMATION CURRENCY. 107.-109. RESERVED
SECTION 2. RESPONSIBILITIES
110. FLIGHT STANDARDS SERVICE (AFS-1)
110. FLIGHT STANDARDS SERVICE (AFS-1)
Page No.
1-1
1-1
.1-1 1-1 1-1 1-1 1-2 .1-3 1-3 .1-4
.1-5
1-5 .1-5
111. FLIGHT TECHNOLOGIES AND PROCEDURES DIVISION (AFS-400)
112. REGIONAL FLIGHT STANDARDS DIVISIONS (AXX-200) 113. AVIATION SYSTEM STANDARDS (AVN)... 114. AERONAUTICAL INFORMATION SERVICES (ATA-100) 115. INDIVIDUAL... 116.-119. RESERVED
111. FLIGHT TECHNOLOGIES AND PROCEDURES DIVISION (AFS-400)
.1-5 .. 1-6 .1-7 .1-7 .1-7
SECTION 3. INSTRUMENT APPROACH PROCEDURES AUTOMATION (IAPA)
RESPONSIBILITIES
120. BACKGROUND 121. AVIATION SYSTEM STANDARDS RESPONSIBILITY 122. OFFICE OF INFORMATION SERVICES RESPONSIBILITY.
.1-8
.1-8 .1-8 1-9 .. 1-9
123. OFFICE OF INFORMATION TECHNOLOGY RESPONSIBILITY.
124. DIRECTOR, AIRWAY FACILITIES SERVICE 125.-199. RESERVED
124. DIRECTOR, AIRWAY FACILITIES SERVICE 125.-199. RESERVED
CHAPTER 2. GENERAL PROCEDURES
SECTION 1. GENERAL
200. GENERAL.
1-9 1-9
.2-1
..2-1
.2-1 .2-1
201. REQUESTS FOR PUBLIC-USE INSTRUMENT FLIGHT PROCEDURES.
202. AIR TRAFFIC LETTERS OF AGREEMENT 203. AIRPORT LIGHTING AND VISUAL AIDS.
SECTION 1. GENERAL
SECTION 2. AERONAUTICAL CHARTS.
204. USE OF MAPS AND CHARTS. 205. AERONAUTICAL CHARTS AND PUBLICATIONS
.2-1 .2-1
..2-2
.2-2 .2-2
Page iii
SECTION 3. ENVIRONMENTAL REQUIREMENTS
206. NOISE ABATEMENT 207. ENVIRONMENTAL IMPACTS.
SECTION 4. FACILITY UTILIZATION AND MONITORING
208. FREQUENCY SERVICE VOLUMES.. 209. ATC USABLE DISTANCE AND ALTITUDE LIMITATIONS. 210. REQUESTS FOR EXPANDED SERVICE VOLUMES (ESV). 211. UTILIZATION OF LOCALIZERS AS EN ROUTE AIDS.... 212. MONITORING OF NAVIGATION FACILITIES 213. UTILIZATION OF MONITORING CATEGORIES. 214. UTILIZATION OF 75 Mhz MARKERS
SECTION 4. FACILITY UTILIZATION AND MONITORING
Page No.
2-3 ..2-3
2-4
2-4 2-4 2-5 2-6 2-6 .2-7 .2-7
SECTION 5. IMPLEMENTING EPOCH YEAR MAGNETIC VARIATION (MV)..
215. GENERAL. 216. RESPONSIBILITIES 217. GUIDELINES.... 218.-219. RESERVED
SECTION 6. NOTICES TO AIRMEN (NOTAM).
220. GENERAL. 221. NATIONAL NOTICE TO AIRMEN SYSTEM 222. FDC NOTAM TYPES.
215. GENERAL. 216. RESPONSIBILITIES 217. GUIDELINES.... 218.-219. RESERVED
.2-8
2-8 2-8 2-10 .2-10
.2-11
2-11 2-11 2-11 .2-11
223. FDC NOTAM PREPARATION, REVIEW, AND TRANSMITTAL ...
224. INSTRUMENT PROCEDURE NOTAM'S. 225. AIRWAY NOTAM'S. 226. NOTAM CONTENT. 227. NOTAM FOLLOW-UP ACTION. 228. NOTAM RESPONSIBILITY. 229. RESERVED.
2-12 2-14 .2-15 2-16 2-16 .2-16
SECTION 7. QUALITY/STANDARDIZATION OF INSTRUMENT FLIGHT
SECTION 7. QUALITY/STANDARDIZATION OF INSTRUMENT FLIGHT
PROCEDURES.
230. AVN-100 ACTION 231. AFS-420 ACTION. 232.-239. RESERVED
2-17
2-17 2-17 2-17
SECTION 8. PERIODIC REVIEW OF INSTRUMENT PROCEDURES
240. GENERAL.. 241. AVN-100 ACTION 242.-249. RESERVED
Page iv
2-18
.2-18 .2-18 .2-19
240. GENERAL.. 241. AVN-100 ACTION 242.-249. RESERVED
SECTION 9. COMMUNICATIONS AND WEATHER.
250. COMMUNICATIONS REQUIREMENTS. 251. USE OF UNICOM...
Page No.
.2-20
.2-20 .2-20
252. AUTOMATIC ALTIMETER SETTING AND WEATHER REPORTING
SYSTEMS 253.-259. RESERVED
SECTION 10. NAVIGATIONAL FIXES
260. GENERAL 261. REPORTING POINTS.
.2-20 ..2-20
SECTION 10. NAVIGATIONAL FIXES
.2-21
.2-21 .2-21 .2-21
262. UNPLANNED HOLDING AT DESIGNATED REPORTING POINTS.
263. REQUESTS FOR NAVIGATIONAL FIXES. 264. NAMING NAVIGATIONAL FIXES 265. DOCUMENTING NAVIGATIONAL FIXES
..2-21 ..2-21 .2-21
266. CORRELATION OF NAVIGATIONAL FIXES AND CHANGEOVER
POINTS (COPS).. 267. MINIMUM RECEPTION ALTITUDES (MRA). 268. FLIGHT INSPECTION.. 269. MAXIMUM AUTHORIZED ALTITUDES (MAA) ...
SECTION 11. OBSTACLE DATA ACCURACY
SECTION 11. OBSTACLE DATA ACCURACY
270. GENERAL..
2-22 .2-22 2-22 2-22
.2-23
.2-23
271. OBSTACLE DATA ACCURACY STANDARDS FOR INSTRUMENT
PROCEDURES. 272. APPLICATION. 273.-279. RESERVED
SECTION 12. WAIVER OF STANDARDS
280. GENERAL.. 281. WAIVER PROCESSING
2-23 2-24 .2-25
.2-26
2-26 2-26 2-26
280. GENERAL.. 281. WAIVER PROCESSING
282. WAIVERS FOR SPECIAL INSTRUMENT APPROACH PROCEDURES.
283. PERIODIC REVIEW OF WAIVERS 284. CANCELLATION OF WAIVERS .. 285.-289. RESERVED
2-26 2-26 2-27
2-28
SECTION 13. IAPA PROCEDURES DEVELOPMENT AND PROCESSING
290. GENERAL 291. IAPA RECORDS DISPOSITION. 292.-299. RESERVED
2-28 2-28 .2-28
290. GENERAL 291. IAPA RECORDS DISPOSITION. 292.-299. RESERVED
Page v
CHAPTER 3. EN ROUTE PROCEDURES
SECTION 1. GENERAL
300. GENERAL. 301. PUBLICATION.. 302.-309. RESERVED.
SECTION 2. CRITERIA APPLICATION AND DEVELOPMENT
310. CRITERIA APPLICATION. 311. DEVELOPMENT OF CRITERIA 312.-319. RESERVED
SECTION 3. ESTABLISHMENT OF EN ROUTE AIRSPACE.
310. CRITERIA APPLICATION. 311. DEVELOPMENT OF CRITERIA 312.-319. RESERVED
Page No.
..3-1
.3-1
..3-1 .3-1 .3-1
..3-2
.3-2 .3-2 .3-2
.3-3
.3-3
320. RELATIONSHIP OF COP'S TO AIRSPACE DIMENSIONS
.3-3
321. RELATIONSHIP OF MEA'S TO CONTROLLED AIRSPACE FLOORS
322.-329. RESERVED
.3-3
SECTION 4. SUBSTITUTE EN ROUTE FLIGHT PROCEDURES
330. GENERAL. 331. FORMAT. 332. FACILITIES USED. 333. CONTROLLED AIRSPACE. 334. FLIGHT INSPECTION.. 335. PLANNING AND COORDINATION. 336. PROCESSING.. 337. PERIODIC REVIEW 338. DISTRIBUTION 339. RESERVED.
SECTION 5. OFF-AIRWAY ROUTES
SECTION 5. OFF-AIRWAY ROUTES
340. ESTABLISHMENT. 341. LISTING... 342 OFF-AIRWAY DATA 343. PROCESSING DATA TO NFDC 344.-349. RESERVED
SECTION 6. NEW OR REVISED JET ROUTES
350. COORDINATION PROCEDURES 351. PUBLICATION OF PROCEDURAL DATA 352.-359. RESERVED
Page vi
.3-4
..3-4 .3-4 .3-4 .3-4 ..3-4 .3-4 .3-8 .. 3-8 .. 3-8 ..3-8
350. COORDINATION PROCEDURES 351. PUBLICATION OF PROCEDURAL DATA 352.-359. RESERVED
.. 3-9
..3-9 .3-9 ..3-9 .3-9 .. 3-9
.3-10
..3-10 .3-10 .3-10
SECTION 7. RADAR VECTORING ALTITUDE CHARTS.
360. CHART PREPARATION 361. AREAS OF CONSIDERATION. 362. OBSTACLE CLEARANCE.. 363. OBSTACLE CLEARANCE REDUCTION.. 364. RADAR DATA PROCESSING (RDP).. 365. CHART REVIEW AND APPROVAL. 366. EMERGENCY OBSTRUCTION VIDEO MAP (EOVM) 367.-369. RESERVED
CHAPTER 4. TERMINAL PROCEDURES
CHAPTER 4. TERMINAL PROCEDURES
SECTION 1. GENERAL.
400. GENERAL.
Page No.
.3-11
..3-11 .3-11 .3-11 ..3-11 ..3-11 ..3-12 .3-12 .3-12
.4-1
.4-1
.4-1 .4-1
401. CATEGORIES OF INSTRUMENT APPROACH PROCEDURES..
402. AIRSPACE REQUIREMENTS 403 CONTRACTUAL USE OF PRIVATE FACILITIES 404. TERPS APPLICATION. 405. SIDESTEP MANEUVERS 406.-419. RESERVED
.4-1 .4-1 4-1 ..4-6 4-7
4-8
SECTION 2. STANDARD INSTRUMENT APPROACH PROCEDURES (SIAP).
420. GENERAL.
.4-8 .4-8
421. COORDINATION OF TERMINAL INSTRUMENT PROCEDURES.
422. RADAR INSTRUMENT APPROACH PROCEDURES. 423.-429. RESERVED
422. RADAR INSTRUMENT APPROACH PROCEDURES. 423.-429. RESERVED
SECTION 3. VISUAL DESCENT POINT (VDP)
430. ESTABLISHMENT. 431. FAA FORM 8260-9 ENTRIES 432.-439. RESERVED
4-8 4-8
4-9
4-9 4-9 4-9
4-10
SECTION 4. SPECIAL PROCEDURE PROCESSING INSTRUCTIONS
440.-449. RESERVED
SECTION 5. DIRECTION FINDING (DF) PROCEDURES
SECTION 5. DIRECTION FINDING (DF) PROCEDURES
450. GENERAL 451. FORMAT.. 452. APPLICATION OF CRITERIA 453. DF VECTORING ALTITUDES 454. DF VECTOR AREA.
4-10
4-11
4-11 4-11 4-11 4-11 .4-11
Page vii
455. DISTRIBUTION 456 CANCELLATION OF DF PROCEDURES. 457.-459. RESERVED
SECTION 6. CATEGORY (CAT) II AND III ILS.
460. GENERAL. 461. ACTION .. 462. RADIO ALTIMETER HEIGHTS 463. NOTAM REQUIREMENTS. 464. WAIVER REQUIREMENTS. 465.-469. RESERVED.
455. DISTRIBUTION 456 CANCELLATION OF DF PROCEDURES. 457.-459. RESERVED
SECTION 7. DEPARTURE PROCEDURES (DP).
470. GENERAL 471. PUBLICATION. 472.-479. RESERVED
Page No.
4-12 4-12 4-12
4-13
4-13 .4-13 4-14 .4-14 .4-14 .4-14
.4-15
.4-15 4-16 4-17
4-18
SECTION 8. STANDARD TERMINAL ARRIVAL ROUTES (STAR).
480. INTRODUCTION 481. AVN-100 ACTION 482. - 499. RESERVED
CHAPTER 5. AIRSPACE
CHAPTER 5. AIRSPACE
SECTION 1. OBSTRUCTION EVALUATION (OE)
500. GENERAL.
4-18 4-18 4-18
..5-1
..5-1
.5-1 .5-1
501. RESPONSIBILITY AND PROCESSING OF FAA FORM 7460-1.
502. REVIEW OF NOTICES. 503. OBSTRUCTIONS UNDER SUBPART C. 14 CFR PART 77 .
SECTION 2. DESIGNATION OF CONTROLLED AIRSPACE
504. GENERAL 505. AT RESPONSIBILITY 506. AVN-100 ACTION.. 507. TERMINAL AIRSPACE
504. GENERAL 505. AT RESPONSIBILITY 506. AVN-100 ACTION.. 507. TERMINAL AIRSPACE
SECTION 3. AIRPORT AIRSPACE ANALYSIS
508. GENERAL.
.5-1 .5-2
.5-3
.5-3 .5-3 .5-3 .5-3
..5-17
..5-17
509. AVN-100 INPUTS IN ESTABLISHMENT OF AIRPORTS AND HELIPORTS .... 5-17
510. ALTERATIONS OF AIRPORTS OR HELIPORTS.
509. AVN-100 INPUTS IN ESTABLISHMENT OF AIRPORTS AND HELIPORTS .... 5-17
Page viii
..5-18
511. DEACTIVATION OF AIRPORTS OR HELIPORTS 512. ASSISTANCE IN ZONING PROBLEMS.
SECTION 4. CONTROLLED FIRING AREAS.
513. DESCRIPTION 514. ESTABLISHMENT OF CONTROLLED FIRING AREAS.... 515. PRECAUTIONS.. 516. AVN-100 REVIEW AND COORDINATION..
SECTION 5. RESTRICED AREAS
SECTION 5. RESTRICED AREAS
517. GENERAL. 518 LETTER OF PROCEDURES.. 519. RESERVED.
Page No.
.5-18 .5-18
.5-19
.5-19 .5-19 .5-19 .. 5-19
.5-20
.5-20 ..5-20 ..5-20
SECTION 6. ESTABLISHMENT, RELOCATION, OR DISCONTINUANCE OF
RADIO NAVIGATION AIDS
520. CRITERIA AND GUIDELINES. 521. AVN-100 ACTION. 522. AFS ACTION.. 523.-599. RESERVED
520. CRITERIA AND GUIDELINES. 521. AVN-100 ACTION. 522. AFS ACTION.. 523.-599. RESERVED
CHAPTER 6. MILITARY PROCEDURES.
600. GENERAL. 601. REVIEW AND COORDINATION.. 602. FAA ACCEPTANCE 603. ASSISTANCE.. 604. - 699. RESERVED
CHAPTER 7. PLANNING
SECTION1. GENERAL
700. GENERAL.
SECTION 2. PLANNING STANDARDS
701. PLANNING STANDARDS
.5-21
.5-21 .5-21 .5-21 .5-21
6-1 (and 6-2)
701. PLANNING STANDARDS
6-1 6-1 .6-1 6-1 .6-1
7-1
7-1
7-1
7-2
7-2 7-2
702. DETERMINATION OF OPERATIONAL BENEFITS/IMPROVEMENTS
SECTION 3. SAFETY ANALYSIS
703. PERFORMING SAFETY ANALYSIS.
7-3
7-3
Page ix
SECTION 4. AIRWAY PLANNING.
704. GENERAL..
SECTION 5. TERMINAL PLANNING.
705. GENERAL
Page No.
.7-5
7-5
705. GENERAL
7-6
7-6
706. REQUIREMENTS FOR OUTER COMPASS LOCATORS FOR NEW ILS
INSTALLATIONS
SECTION 6. AIRPORT PLANNING
707. GENERAL.
SECTION 7. PRIVATE AID.
708. GENERAL.
SECTION 8. FACILITY AND EQUIPMENT (F&E) SUPPORT.
709. SUPPORT. 710.-799. RESERVED
7-6
7-12
7-12
7-13
7-13
7-14
7-14 7-14
CHAPTER 8. INSTRUMENT APPROACH PROCEDURES DATA TRANSMITTAL
CHAPTER 8. INSTRUMENT APPROACH PROCEDURES DATA TRANSMITTAL
SYSTEM..
SECTION 1. GENERAL
800. GENERAL`
SECTION 2. FORM USE AND PREPARATION.
801. USE OF FORMS 802. FORM PREPARATION..
8-1
.8-1
8-1
.8-2
8-2 8-2
803. AIRPORT DATA REQUIREMENTS FOR INITIAL INSTRUMENT APPROACH
PROCEDURE SERVICE. 804. COURSE AND DISTANCE INFORMATION 805. COMMUNICATIONS DATA 806. NOS OBSTACLE DATA. 807. TERMINAL ROUTES GENERAL 808. TERMINAL FIXES.
803. AIRPORT DATA REQUIREMENTS FOR INITIAL INSTRUMENT APPROACH
SECTION 3. COMPLETION OF FAA FORMS 8260-3/5..
809. GENERAL. 810. TERMINAL ROUTES
Page x
8-3 8-4 8-4 .8-4 .8-4 .8-7
.8-9
8-9 8-9
12/29/99 8260.19C CHG 2
Page No.
811. LINES 1 THROUGH 8... .8-10 812. TAKEOFF AND ALTERNATE MINIMUMS .8-13 813. MINIMUMS. .8-14 814. NOTES 8-19 815. MISSED APPROACH … 8-22 816. ADDITIONAL FLIGHT DATA .. .. 8-24 817. LOWER BLOCKS .8-26 818.-830. RESERVED .8-28
SECTION 4. COMPLETION OF FAA FORMS 8260-4/7/10/15 .8-29
SECTION 4. COMPLETION OF FAA FORMS 8260-4/7/10/15 .8-29
831. GENERAL.. .8-29 832. FAA FORM 8260-4, RADAR.... 8-29 833. FAA FORM 8260-7, SPECIAL INSTRUMENT APPROACH PROCEDURE. ..8-30 834. FAA FORM 8260-10, CONTINUATION SHEET. .8-32 835. FAA FORM 8260-15, DEPARTURE PROCEDURES/TAKEOFF MINIMUMS … 8-32
SECTION 5. CERTIFICATION, PROCESSING, AND REVIEW .8-35
SECTION 5. CERTIFICATION, PROCESSING, AND REVIEW .8-35
836. GENERAL. .8-35 837. CERTIFICATION AND DISTRIBUTION OF SIAP's .8-35 838. CANCELLATION OF INSTRUMENT APPROACH PROCEDURES.. ..8-36 839. MINOR REVISIONS TO SIAP' .. ..8-36 840 PROCESSING. 8-36 841. FIO AND FPB REVIEW OF SIAP's AND CHARTS. .8-37 842.-899. RESERVED .8-37
CHAPTER 9. FORMS AND FORM USE. .9-1
CHAPTER 9. FORMS AND FORM USE. .9-1
SECTION 1. PROCEDURES FORM PROCESSING .9-1
900. INTRODUCTION .9-1 901. FIO ACTION … 9-1
SECTION 2. EXPANDED SERVICE VOLUME REQUEST, FAA FORM 6050-4 .9-2
902. PREPARATION OF FAA FORM 6050-4 ..9-2
SECTION 3. FLIGHT PROCEDURES STANDARDS WAIVER, FAA FORM 8260-1, (RIS:FS8220-7). .9-4
903. PREPARATION OF FAA FORM 8260-1, FLIGHT PROCEDURES STANDARDS WAIVERS .. 9-4
903. PREPARATION OF FAA FORM 8260-1, FLIGHT PROCEDURES STANDARDS WAIVERS .. 9-4
SECTION 4. RADIO FIX AND HOLDING DATA RECORD, FAA FORM 8260-2... .9-12
904. INTRODUCTION. 9-12 905. PREPARATION OF FAA FORM 8260-2 .. 9-12
Page xi
8260.19C CHG 2 12/29/99
Page No.
906. CANCELLATION. 9-18 907. GENERAL.. 9-18
SECTION 5. FORM LETTER FOR COORDINATION OF SIAP's .. .9-19
SECTION 5. FORM LETTER FOR COORDINATION OF SIAP's .. .9-19
908. PREPARATION OF COORDINATION LETTER . .9-19
SECTION 6. STANDARD INSTRUMENT APPROACH PROCEDURE DATA RECORD, FAA FORM 8260-9 (RIS: FS 8260-7) .. .9-21
909. PREPARATION OF FAA FORM 8260-9. 9-21
SECTION 7. TRANSMITTAL OF AIRWAYS-ROUTE DATA, FAA FORM 8260-16.... 9-25
910. PREPARATION OF FAA FORM 8260-16 .. 9-25 911.-999. RESERVED .9-27
910. PREPARATION OF FAA FORM 8260-16 .. 9-25 911.-999. RESERVED .9-27
APPENDIX 1. FLIGHT PROCEDURES REFERENCES (4 Pages)
ORDERS AND NOTICES. .2 ADVISORY CIRCULARS. .3 FEDERAL AVIATION REGULATIONS (FAR's) ... .4 OTHER PUBLICATIONS. 4
APPENDIX 2. OBSTACLE ACCURACY STANDARDS, CODES, AND SOURCES (5 Pages)
APPENDIX 2. OBSTACLE ACCURACY STANDARDS, CODES, AND SOURCES (5 Pages)
100. UNITED STATES NATIONAL MAP ACCURACY STANDARDS. 2 101. ACCURACY CODES AND SOURCES.. .2
APPENDIX 3. DIRECTIVE FEEDBACK INFORMATION, FAA FORM 1320-19 (2 Pages)
Sample FAA Form 1320-19.. 2
APPENDIX 4. RADIO FIX AND HOLDING DATA RECORD, FAA FORM 8260-2 (13 Pages)
Sample FAA Forms 8260-2 (Front side only) . ...2 Sample FAA Forms 8260-2 (Front and Back). ..3 and 4 Sample FAA Forms 8260-2 (Front side only) ... 5 thru 8 Sample FAA Forms 8260-2 (Front and Back). ..9 thru 12 Sample FAA Form 8260-2 (Cancellation) … 13
APPENDIX 5. ILS - STANDARD INSTRUMENT APPROACH PROCEDURE, FAA FORM 8260-3 (9 Pages)
APPENDIX 5. ILS - STANDARD INSTRUMENT APPROACH PROCEDURE, FAA FORM 8260-3 (9 Pages)
Sample FAA Forms 8260-3 (Front side only) . . 2 thru 7 Sample FAA Form 8260 3 (Pages 1 and 2) . .. 8 and 9
Page xii
Page No.
APPENDIX 6. RADAR - STANDARD INSTRUMENT APPROACH PROCEDURE,
FAA FORM 8260-4 (5 Pages)
Sample FAA Form 8260-4 (Pages 1 and 2) ..
...2 thru 5
APPENDIX 7. STANDARD INSTRUMENT APPROACH PROCEDURE,
FAA FORM 8260-5 (16 Pages)
Sample FAA Form 8260-5 (Front side only) . Sample FAA Form 8260-5 (Pages 1 and 2) ..
..2 thru 14 ... 15 and 16
APPENDIX 8. SPECIAL INSTRUMENT APPROACH PROCEDURE,
FAA FORM 8260-7 (3 Pages)
Sample FAA Form 8260-7 (Front and Back sides)
..2 and 3
APPENDIX 9. STANDARD INSTRUMENT APPROACH PROCEDURE DATA RECORD,
FAA FORM 8260-9 (5 Pages)
Sample FAA Forms 8260-9 (Front and Back sides) ..
APPENDIX 10. EMERGENCY DF APPROACH PROCEDURE, FAA FORM 8260-10 (2 Pages)
APPENDIX 10. EMERGENCY DF APPROACH PROCEDURE, FAA FORM 8260-10 (2 Pages)
Sample FAA Form 8260-10
...2 thru 5
..2
APPENDIX 11. DEPARTURE PROCEDURES / TAKEOFF MINIMUMS
FAA Form 8260-15 (3 Pages)
Sample FAA Forms 8260-15
. 2 and 3
Page xiii (and xiv)
CHAPTER 1. ADMINISTRATIVE
SECTION 1. GENERAL
100. PURPOSE
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 to offices on special mailing list ZVN-826.
102. CANCELLATION. Order 8260.19B, Flight Procedures and Airspace, dated December 18, 1991, is canceled.
103. EXPLANATION OF CHANGES.
a. Use of maps and charts clarified.
b. Expanded service volume (ESV) distribution modified.
c. Use of Notice to Airmen (NOTAM) system modified.
d. Airway NOTAM'S introduced with examples.
e. Periodic (annual) standard instrument approach procedure (SIAP) review interval extended to two years; airway review interval to four years.
f. Instrument Approach Procedures Automation (LAPA) procedure development and storage clarified.
g Instructions for reporting IAPA equipment or communications problems added.
h. All references to control zones changed to "Class B/C/D/E Surface Areas;" and references to transition areas changed to “Class E 700’ airspace."
i. Flight Inspection Office (FIO)/Air Traffic Control (ATC) actions regarding minimum vector
altitude (MVA) / Minimum IFR Altitude (MIA) charts clarified.
j. Instructions regarding area navigation (RNAV) feeder routes incorporated.
k. Requirement for drawings with airspace packages deleted.
L Rounding convention clarified.
m. Terminal distance measuring equipment (DME) fix designations clarified.
n. "LOC only” notation clarified.
o. Alternate minimums notation clarified.
p. Dual minimums notes clarified.
q. Inoperative component notes clarified.
r. Automatic weather observation system (AWOS) instructions modified.
s. Additional flight data block instructions for LORAN-C added.
t. FAA Form 8260-2 controlling obstruction documentation clarified.
u. FAA Form 8260-9 required obstruction clearance (ROC) and height of missed approach surface (HMAS) documentation clarified.
v. FAA Form 8260-16 changeover point (COP) instructions clarified; flight inspection date and cancellation instructions clarified.
w. Numerous flight procedure references added to appendix 1.
L. FAA 8260-series forms examples udpated.
104. FORMS.
a. The following forms are stocked at the FAA Logistics Center (AML), or provided in electronic form for use in the development and maintenance of flight procedures
NATIONAL STOCK NUMBER(NSN)
UNIT OF ISSUE
FAA FORM NUMBER
FAA Form 8260-1
FAA FORM NUMBER
FAA Form 8260-2
FAA Form 8260-3
FAA Form 8260-4
FAA Form 8260-5
FAA Form 8260-7
FAA Form 8260-8
FAA Form 8260-9
FAA Form 8260-10
FAA Form 8260-11
FAA Form 8260-12
FAA Form 8260-13
FAA Form 8260-15
FAA Form 8260-16
FAA Form 8260-20
TITLE
Flight Procedures Standards Waiver
Radio Fix and Holding Data Record
ILS-Standard Instrument Approach Procedure
Radar-Standard Instrument Approach Procedure
Standard Instrument Approach Procedure
Special Instrument Approach Procedure
Form Letter for Coordination of SIAP
Standard Instrument Approach Procedure Data Record
Standard Instrument Approach Procedure (Continuation Sheet)
U.S. Army ILS Standard Instrument Approach Procedure
U.S. Army Radar Standard Instrument Approach Procedure
U.S. Army Standard Instrument Approach Procedure
Departure Procedures/Takeoff Minimums
Transmittal of Airways/Route Data
U.S. Army Standard Instrument
0052-00-661-8001
0052-00-606-9001
0052-00-691-2003
0052-00-691-3001
0052-00-677-7002
0052-00-684-3001
0052-00-683-5000
0052-00-684-6000
0052-00-691-4002
0052-00-803-1001
0052-00-803-2001
0052-00-803-3001
0052-00-838-8001
0052-00-634-4001
0052-00-856-5000
SH
SH
SH
SH
SH
SH
SH
SH
SH
SH
SH
SH
SH
SH
SH
Approach Procedure(Continuation Sheet)
FAA Form 8260-21
FAA Form 8260-22
U.S. Army Departure Procedures/ Takeoff
MLS-Standard Instrument Approach Procedure
0052-00-856-6000
0052-00-889-8000
SH
SH
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 filling procedures forms either by hand or 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 Automation Technology Branch, AVN-22A.
(3) Equipment Requirements. Each user office must have access to the appropriate hardware/software to use automated electronic forms software. Contact AVN-22A 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. IAPA Generated Forms. Refer to chapter 2, section 13.
105. TERMS AND DEFINITIONS.
For the purpose of this order, flight procedures are identified as the functions for predetermining safe and practical methods of navigating aircraft which 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. Shall - action is mandatory.
c. Should – action is desirable.
d. Will – indicates a presumption that action is to be taken.
e. AWOP – All Weather Operations Program.
f. 14 CFR - Title 14 of the Code of Federal Regulations.
g. FICO - Flight Inspection Central Operations Office, AVN-250.
h. Flight Inspection Operations Division, AVN-200.
i. FPO – Flight Procedures Office.
j. LAPA - Instrument Approach Procedures Automation.
k. Miles - nautical miles unless otherwise specified.
1. NFDC – National Flight Data Center, ATA-110.
m. NTAP - Notices to Airmen Publication.
n. NFPO – National Flight Procedures Office, AVN-100.
o. SIAP - Standard I Instrument Approach Procedure.
p. USNOF – U.S. NOTAM Office.
106. INFORMATION CURRENCY.
a. Forward for consideration any deficiencies found, clarification needed, or suggested improvements regarding the contents of this order to:
DOT/FAA Flight Procedure Standards Branch, AFS-420 P.O. Box 25082 Oklahoma City, OK 73125
b. Your assistance is welcome. FAA Form 1320-9, Directive Feedback Information, is included at the end of this order for your convenience If an interpretation is needed immediately, you may call the originating office for guidance. However, you should use the FAA Form 1320-9 as a follow-up to the verbal conversation.
8260.19C CHG 2 12/29/99
c. Use the “Other Comments" block of this form 107-109. RESERVED providing a complete explanation of why the suggested change is necessary.
Page 1-4 Chap 1 Par 106
SECTION 2. RESPONSIBILITIES
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.
110. FLIGHT STANDARDS SERVICE (AFS-1)
b. Responsibility for the overall management of the Flight Procedures and Airspace Program is vested in the Flight Technologies and Procedures Division (AFS-400). This order is primarily concerned with those offices having direct responsibility for the accomplishment of the Flight Procedures and Airspace Program. The following is a brief description of their activities.
111. FLIGHT TECHNOLOGIES AND PROCEDURES DIVISION (AFS-400).
a. This division is the principal element of the Flight Standards Service governing policies, criteria, and standards for establishing and maintaining terminal and en route flight procedures; for using air navigation facilities, appliances, and systems; and for certification of LAPA software. This office is designated as the final authority to issue, amend and appeal minimum en route IFR altitudes and associated flight data under 14 CFR part 95 and standard instrument approach procedures under 14 CFR part 97. The division is also responsible for approval/ disapproval of special instrument approach procedures and requests for waivers of standards.
b. The Flight Operations Branch, AFS-410, is the principal element of the division with respect to concepts, policies, systems, and programs associated with the operational and flight technical aspects of all weather operations. It develops concepts for design, evaluation, and approval of Category I, II, and III approach and landing operations, as well as lower than standard takeoff minimums.
c. The Flight Procedure Standards Branch, AFS-420, is the principal element within the division, with respect to the rulemaking process of the Flight Procedures Program; also with respect to the development, application, and oversight of national policies and directives for the administration of the national flight procedures program, and development of criteria pertinent to the design of instrument flight procedures; and with respect to testing, data analysis, verification, and validation of navigation systems and concepts. 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. It participates as the division focal point in the waiver review process, soliciting comments from appropriate FAA offices, providing operational input, and recommending the division final waiver approval/disapproval. The branch provides 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. It also provides for the technical evaluation and risk assessment of proposed instrument operations not covered by standard criteria.
112. REGIONAL FLIGHT STANDARDS DIVISIONS (AXX-200)
112. REGIONAL FLIGHT STANDARDS DIVISIONS (AXX-200)
a. The Regional Flight Standards Divisions (FSD) manage and direct the geographic regions' air carrier, general aviation and all weather operations programs. Each FSD 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.
(3) Coordinating the FSD portion of assigned foreign instrument approach procedures programs.
(4) Coordinating the FSD involvement in Category 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 Airports Division, as necessary.
(7) Providing the consolidated FSD 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 Airway Facilities Division's submission of a NAS Change Proposal (NCP).
(10) When requested by the FPO, assists in developing the equivalent level of safety for an AVN originated procedures waiver.
113. AVIATION SYSTEM STANDARDS (AVN).
a. AVN is the principal element within Airway Facilities Service (AAF) 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 regional Airway Facilities Division Facilities and Equipment (F&E) budget submission with respect to terminal air navigation aids (other than radar) and visual approach aids. Additionally, AVN supports the Air Traffic Services (ATS) obstruction evaluation and airport airspace analysis (OE/AAA) program.
b. The National Flight Procedures Office, AVN-100, is the AVN element responsible for the development, maintenance, quality control, and technical approval of public-use instrument procedures. It is also responsible for quality control and technical support, as requested, for NAS related products. Upon completion of instrument procedures development, the division forwards completed documentation to the FICO for flight inspection and operational approval. Establishes procedures to ensure GPS data is included in the national database. Responsibilities include but are not limited to:
(1) Forwarding industry and user comments on instrument procedures to the appropriate branch manager for evaluation and processing.
(2) Coordinating requests for new instrument procedures service with the respective regional division and other concerned offices, and conducting instrument procedures feasibility studies.
(3) Coordinating submission by responsible offices of all pertinent data and supporting documents required for procedures development and assignment of priority when further procedures action is required.
(4) Planning and coordinating new or relocated NAS facilities.
(5) Coordinating with regional divisions to select a charting date consistent with priorities and workload when a component of the National Airspace System (NAS) is to be commissioned, decommissioned, or altered.
(6) Coordinating the input for the planning and development of regional F&E budget submissions and programming actions.
(7) 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.
(8) Evaluating regional airport and airspace matters.
(9) Determining the necessity for environmental impact studies as required by current policy.
(10) Acting as focal point for flight inspection problems within the region.
c. The Flight Inspection Operations Division, AVN-200, is the AVN element responsible for flight inspection of navigation aids and flight procedures in support of the NAS. The division 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 AVN-100, 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.
114. AERONAUTICAL INFORMATION SERVICES (ATA-100).
a. This is the principal element within Air Traffic Service (AAT) directly responsible for managing the agency's program to provide aeronautical infor-mation services to ensure the flow of information necessary for safety, regularity, and efficiency of air navigation. This division is charged with the responsibility for collecting, collating, validating and disseminating aeronautical data regarding the United States and its territories. It is also a source for technical assistance to AVN regarding data base accuracy standards, content, and format. This division also serves as the primary interface between the FAA and the National Oceanic and Atmospheric Administration for government aeronautical charting services.
b. The National Flight Data Center, ATA-110, is the principal element within ATA-100 with respect to maintaining the national aeronautical information data base 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 elements of the NAS.
(2) Conducting pre-publication review of aeronautical data contained in standard instrument
approach and departure procedures, standard terminal arrival routes, standard instrument departures, military training routes, navigational aids, airport data, and airspace actions submitted for action, and to identify and correct items in nonconformance with applicable directives.
(3) Validating submitted data with the National Data Base and resolving contradictions.
(4) Reviewing, processing for transmittal, and tracking NOTAM's regarding amendments, cancellations, and corrections to instrument procedures in the NAS and canceling these NOTAM's when government charts are updated.
(5) Compiling NOTAM's 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 SIAP's with assigned effective dates in a bi-weekly transmittal letter and completing necessary requirements for publication in 14 CFR part 97.
(8) Issuing, on a predetermined schedule, amendments to 14 CFR part 95.
(9) Maintaining copies of 8260 and 7100 series forms that support public use SLAP's, fixes, airways, STAR's and DP's (SID's).
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 shall 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.
SECTION 3. INSTRUMENT APPROACH PROCEDURES AUTOMATION (IAPA) RESPONSIBILITIES
SECTION 3. INSTRUMENT APPROACH PROCEDURES AUTOMATION (IAPA) RESPONSIBILITIES
120. BACKGROUND.
a. The FAA has developed IAPA to automate the mechanics of the Instrument Flight Procedures Program to include the development, review, storage, and electronic transmittal of instrument flight procedures with ancillary system benefits.
b. The. LAPA system standardizes the application of criteria specified in FAA Order 8260.3, United States Standard for Terminal Instrument Procedures (TERPS); FAA Order 8260.19, Flight Procedures and Airspace; and other appropriate directives, advisory circulars, and Federal Aviation Regulations. IAPA applies established FAA software standards. LAPA software provides for application of standardized data and data accuracy standards in the development of instrument flight procedures.
c. IAPA includes obstacles, terrain, NAVAID, fix, holding, airport, and runway data that are available to system users. IAPA is included in the FAA's Capital Investment Plan (CIP). Procedures for controlling changes to this system will be in accordance with FAA Order 1370.52, Information Resources Policy.
121. AVIATION SYSTEM STANDARDS RESPONSIBILITY.
The Aviation System Standards, AVN-1, is the office of primary interest and is responsible for overall functional management of the LAPA system and has been delegated responsibility for certification of IAPA software (see paragraph 121b(7)).
a. The Resource Management Staff, AVN-20, is responsible for establishing policy guidance in the administrative control of LAPA, as well as coordinating actions required to meet changing legal and user requirements. In addition, this division is responsible for:
(1) Carrying out the development of LAPA by coordinating the efforts of users, developers, operators, and contractors associated with LAPA.
(2) Managing and reporting on project schedules, costs, and other supporting resources for the Airway Facilities Service (AAF) 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 LAPA system) 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 operational tests and evaluations of the information system.
b. The Automation Technology Branch, AVN-22, is responsible for assuring the successful ongoing operation of the data system. In the performance of these responsibilities, the Automation Technology Branch shall:
(1) Establish and maintain a positive change control management system to assure that all changes to the operational LAPA system are cost effective and are coordinated among all parties who use IAPA.
(2) Develop necessary guidelines for the control and dissemination of data from LAPA and other assigned systems.
(3) Authorize release of data in special cases where guidelines are not available.
(4) Provide for coordination in data systems where several program elements share primary operational interest.
(5) Establish priorities for task assignments, scheduling, and utilization of personnel and physical resources.
(6) Assure system configuration, documentation, and reliability.
(7) Conduct extensive operational testing and debugging, to assure system software is in conformance with Order 8260.3, United States Standard for Terminal Instrument Procedures (TERPS) 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 FAA Order 1600.54B, FAA Automated Information Systems Security Handbook, are complied with in the security control of computer programs and associated documentation.
c. The Flight Inspection Technical Support Branch, AVN-210, is responsible for establishing and maintaining the Aviation Standards Information System (ASIS) in support of IAPA requirements.
d. AVN-100 is responsible for final certification of instrument flight procedures to include that:
(1) Data used to develop the instrument approach procedure was correct.
(2) The instrument approach procedure was developed in accordance with FAA Order 8260.3; Order 8260.19, Flight Procedures and Airspace; and other appropriate directives, advisory circulars, and Federal Aviation Regulations listed in appendix 1.
(3) The appropriate Flight Procedures Standards Waiver, if required, is on file.
122. OFFICE OF INFORMATION SERVICES RESPONSIBILITY. 410 The Office of Information Services, AMI-1, is responsible for the software development from its
inception through implementation. It is also responsible for maintenance of system software, and shall provide and control automatic data processing (ADP) resources which 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 LAPA.
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 the United States Standard for Terminal Instrument Procedures and other appropriate directives, advisory circulars, and Federal Aviation Regulations as advised by the program office.
123. OFFICE OF INFORMATION TECH- NOLOGY RESPONSIBILITY.
The Office of Information Technology, AIT-1, will develop governing policies and responsibilities for automatic data processing (ADP) program management in accordance with Order 1370.52, Information Resources Policy.
124. DIRECTOR, AIRWAY FACILITIES SERVICE.
The Director, Airway Facilities Service, AAF-1, is responsible for the determination of agency-wide priorities for use and control of telecommunications resources needed to support IAPA. This responsibility is administered through the Telecommunications Integrated Product Team in the NAS Operations Program (AOP) of Airway Facilities.
125-199. RESERVED.
CHAPTER 2. GENERAL PROCEDURES
CHAPTER 2. GENERAL PROCEDURES
SECTION 1. GENERAL
200. GENERAL.
This chapter provides guidelines and procedures which are common to all instrument flight procedures. Specific guidelines and procedures for en route and terminal instrument flight procedures are contained in chapters 3 and 4, respectively.
SECTION 1. GENERAL
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, paragraph 121.
b. All requests for public-use instrument flight procedures receiyed by any FAA office shall be forwarded to AVN-100 for further handling. Requirements for approval of instrument approach procedures are contained in Chapter 1 of Order 8260.3.
c. Procedures with specific effective dates, and other urgent projects, will be assigned priorities by AVN-100. All other projects will be processed as workload permits, in order of AVN-100 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 AVN-100.
a. When these letters are received, AVN-100 shall review them to ensure compatibility with published or planned flight procedures.
b. Copies of letters of agreement received in AVN-100 shall 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, AVN-100 shall return the letters to the ATC facility with a memorandum which 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 AVN-100 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 Orders:
(1) 7110.10, Flight Services.
(2) 7110.65, Air Traffic Control.
(3) 7210.3, Facility Operation 1and 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
204. USE OF MAPS AND CHARTS.
SECTION 2. AERONAUTICAL CHARTS
a. AVN-100 should maintain an adequate supply of current charts 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), a WAAS precision survey, 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 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 IAPA, AMIS, Quarterly 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 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 and Standards Branch (AVN-230). See FAA Order 8200.1, United States Standard Flight Inspection Manual, paragraph 214.2.
205. AERONAUTICAL CHARTS AND PUBLICATIONS.
a. Aeronautical charts used for air navigation are generally of two groups: VFR charts and IFR charts. The VFR charts are the Sectional and VFR Terminal Area charts and the visual navigation chart. IFR charts are the En Route Low and High Altitude, Area, Instrument Approach Procedure, DP/SID, and STAR charts.
b. Tue 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-420 personnel should conduct surveillance of the AIM and AIP to verify the accuracy and appropriateness of the information therein.
c. AVN-100 personnel should monitor charts | or publications released by FAA which provide informative material, recommended or mandatory, to determine that safe operating practices and conditions are accurately described for aviation users.
d. AVN-100 is responsible for the accuracy and completeness of flight data submitted by that office for publication. Procedure specialists should review the resulting NOS charts to ensure correct portrayal. AVN-100 serves as the focal point for questions about the data published on these charts.
e. Any FAA personnel, who find or are notified of discrepancies and/or errors in aeronautical charts, the AIM, or AIP, should forward the information to AFS-420, or the NFDC.
SECTION 3. ENVIRONMENTAL REQUIREMENTS
206. NOISE ABATEMENT.
The establishment of noise abatement procedures is the responsibility of Air Traffic Service. However, the Flight Standards Service has an input from an aircraft operational standpoint. These procedures should be coordinated between the appropriate regional FSD and the regional FPO. The regional FSD shall review noise abatement procedures for aircraft performance characteristics and operational safety considerations. The regional FPO shall 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.
SECTION 3. ENVIRONMENTAL REQUIREMENTS
207. ENVIRONMENTAL IMPACTS.
FAA Order 1050.1, Policies and Procedures for Considering Environmental Impacts, describes the requirements for documentation of environmental impact or lack of impact concerning actions taken by regional FPO's. In particular, appendix 4 of the document defines actions that require an environmental assessment or a declaration of categorical exclusion. [See also paragraph 800.] AVN will normally act as responsible federal official (RFO) for all AVN and non-AVN developed procedures. In such capacity, AVN shall apply national environmental standards and policies. However, AFS reserves the right to act as RFO for selected non-AVN 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. This order is primarily used by the Regional Frequency Management Officer (FMO). AVN-100 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 (ESV's). The operational service volume shall 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 shall not be used as a.substitute for an approved ESV. See figures 2-1, 2-2, and 2-3.
a. VOR/VORTAC/TACAN
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.
100 nm (185 km)
60,000 ft (18.288 m) 130 nm (241 km)
45,000 ft (13,716 m)
18.000 ft (5.486 m)
40 nm (74.1 km) 14,500 ft (4.420 m) 1,000 f1 (305 m)
Figure 2-1. STANDARD CLASS L/H SERVICE VOLUME
40 nm (74.1 km)
18,000 ft (5.486 m)
1.000 ft (305 m)
Figure 2-2. STANDARD LOW ALTITUDE SERVICE VOLUME
25 nm (46.3 km)
12,000 ft (3.658 m)
1,000 ft (305 m)
Figure 2-3. STANDARD TERMINAL SERVICE VOLUME
b. NDB
Facility Distance Class (Miles)
COMLO NOTE: Low frequency 15 MH beacons have no 25 H standard height 50 HH limitations. 75
c. LS
Height Above Distance Facility Facility (Miles)
Localizer (FC) 4,500 and below 18 Localizer (BC) 4,500 and below 18 Glide Slope (2°-4°) varies with angle 10
d. MLS
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
+40° -40°
20 NM *BACK AZIMUTH AZIMUTH 0 CENTERLINE EXTENDED
20 FAA WHEN INSTALLED NM
-40 +40
Figure 24. MLS AZIMUTH COVERAGE
20,000 FT
TYPICAL GLIDE PATH
15° 3 0.9
EL 20 NM LOWER LIMIT
Figure 2-5. MLS ELEVATION COVERAGE
EL 20 NM LOWER LIMIT
210. REQUESTS FOR EXPANDED SERVICE VOLUMES (ESV).
a. When ATC requires use of NAVAID's 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 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 ESV's are then reviewed by AVN-100.
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 AVN-100 approval.
c. A requirement for an ESV may be determined by the procedures specialist when developing an instrument procedure; e.g., the instrument procedure is proposed beyond SSV. In this case, the procedures specialist processes an FAA Form 6050-4 to obtain FMO and, in turn, flight inspection approval. An ESV request shall 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. AVN-100 initiates a revised FAA Form 6050-4 and explains the action in the REMARKS box of Part III; e.g., "R-035 changed to R-038 due to variation change to 23E/85 effective 4 AUG 83."
e. Describe holding patterns by an arc and two radials (e.g., 306-322°, 83 NM) which enclose the holding pattern.
f. Preparation. Instructions for preparation of an ESV request are in paragraph 902. Figure 9-2 is a sample request.
g. Distribution. The FAA Form 6050-4 is supplied in 6-sheet sets. See paragraph 902e for specific distribution instructions.
h. AVN-100 Periodic Review. Review ESV's biennially.
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 shall start and end at an approved navigational fix.
b. The use of localizers for en route instrument flight procedures shall 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 which causes a facility shutdown when performancedeterioratesbelowestablished tolerances. A remote status indicator may also be provided through the use of a signal sampling receiver, microwave link, or telephone circuit. VOR, VORTAC, and ILS facilities as well as new NDB's and marker beacons, installed by the FAA, are provided with an internal monitoring feature. Older FAA NDB's and some nonfederal NDB's 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 indicate 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. ATC is responsible for issuing NOTAM's 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 shall 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 gudance. See also paragraph 812b.
(2) When a facility is used to designate a stepdown fix, alternate minimums shall 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 shall not be predicated on these facilities.
(5) Navigational fixes developed from crossing radials of Category 3 facilities shall not be used to break a minimum en route altitude (MEA) to
a 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 shall 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.
75 Mhz markers may be utilized as the sole source of identification with the following limitations:
a. Missed Approach Point. Markers may be authorized as missed approach points for nonprecision approaches, provided a remote status indicator (RSI) is installed at an ATC facility.
b. Final Approach Fix. As a nonprecision final approach fix, the marker shall 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 shall not be authorized from a 75 MHz marker.
d. Breaks in MEA's. Fan markers shall 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.)
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.
SECTION 5. IMPLEMENTING EPOCH YEAR MAGNETIC VARIATION (MV)
a Background. The magnetic variation is determined by the National Oceanic and Atmospheric Administration (NOAA) for all areas of the United States and its territories for application to navigation charts and maps. Changing values for MV are tabulated and published on a 5-year epoch basis; e.g., 85, 90, 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 everchanging magnetic field.
b. Participating Offices. Management and control of Epoch Year MV values require action by the following offices:
(1) National Ocean Service (NOS)
(2) Aviation System Standards (AVN)
(3) National Flight Data Center (NFDC)
(4) Regional Airway Facilities Divisions
(5) Regional Airports Divisions
(6) Military Organizations
216. RESPONSIBILITIES.
a. NOS.
(1) Publish isotonic lines or segments thereof on appropriate aeronautical charts based on current Epoch Year values.
(2) Revise en route aeronautical charts to reflect revised MV assignments to navigation facilities in accordance with information published in the National Flight Data Digest (NFDD).
b. AVN.
(1) Function as the focal point for all information relating to application of MV to the following elements of the NAS: navigational aids, airports, and instrument flight procedures; and for coordination and liaison between AVN and the Regional Airports, Air Traffic, and Airway Facilities Divisions 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 adjustment action or MV change is not accomplished by the effective date of amended instrument procedures or revised en route charts.
(4) Assign and maintain MV's of record for navigational facilities (including military facilities) and airports in whole degree increments. MV's of record are available in the AMIS facility data base. 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 is 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 record, the
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° or more between the MV of record and the nearest future Epoch Year value.
(6) Notify NFDC of changes to assigned MV and the effective date of those changes for publication in the NFDD; notify other concerned offices having related responsibilities to ensure timely implementation of necessary actions. The effective date selected shall 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 shall include high and low altitude airways/jet routes, direct routes, air carrier offairway routes, fixes in both high and low altitude structures, terminal routes and fixes, departure procedures (DP's), SID's, STAR's, and any other application to instrument flight procedures. Use the MV of record (or as officially changed) to develop instrument flight procedures - regardless of the MV shown on the 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 IAP's. Modify all 14 CFR Part 95 Direct and Off-Airway (Non-Part 95) routes with documented radial(s) or bearing(s). Change ESV's. Make all modifications to meet an effective date that coincides with the en route change cycle.
NOTE: A listing of affected fixes, holding patterns, DP's, SID's, STAR's, military training routes, preferred routes, and ATS routes may be obtained from NFDC (ATA-110).
(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 816n and 8160).
(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 ESV's.
(d) Amend radar and DF procedures when 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 FAA 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 when the need to change the MV of other military facilities is identified.
(11) Airports.
(a) Amend IAP's, SID's, and DP's which specify runway designator numbers affected by MV change.
(b) Notify the regional 530 office of the need for amendment action if STAR's 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 AVN of any change to MV of record, publish a notice of change in the NFDD to indicate the effective date of such change.
d. Regional Airway Facilities Division. Coordinate with AVN to obtain the MV of record for assignment to newly installed or relocated navigational aids.
e. Regional Airports Division. Coordinate with AVN-160 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 AVN, and be accomplished sufficiently in advance to allow for procedural amendments.
f. Military organizations. Contact AVN-160 to obtain the MV of record to be applied to navigational aids or airports under military jurisdiction.
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. Air Traffic Division may have to initiate or revise published air traffic procedures; Airway Facilities is directly involved in facility rotations and requires proper coordination. The Airports Division may have to arrange for repainting of runway designator numbers.
NOTE: Airport standards require renumbering when the runway designator number is more
than 6° from the magnetic alignment. This is usually accomplished during the next routine repainting, or when the existing markings are obliterated by seal coats, overlays, or reconstruction.
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° or more, the MV of record shall be changed to the nearest future Epoch Year value. When the difference is less than 3°, AVN shall 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) shall 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 shall be used in the development of instrument flight procedures.
d. Runway bearing shall be assigned the same MV as the airport.
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 (NOTAM)
220. GENERAL.
NOTAM's provide timely knowledge to airmen, and other aviation interests, of information or conditions which are essential to safety of flight. NOTAM's 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 procedures for issuing Flight Data Center (FDC) NOTAM's which are required to maintain the accuracy and currency of charted terminal and en route flight procedures.
SECTION 6. NOTICES TO AIRMEN (NOTAM)
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). Details for handling this information are contained in Order 7930.2, Notices to Airmen. The following is a brief summary of the services provided:
a. FDC NOTAM's pertaining to instrument flight procedures are issued through the National Flight Data Center (NFDC) and are primarily used to disseminate safety of flight information relating to regulatory material. They may also be used to provide wide dissemination for flight procedures data, aeronautical information, and other time-critical information. They are numbered by the U.S. NOTAM Office (USNOF) to reflect the year of issuance and the sequence number for the calendar year, (e.g., 8/0445). FDC NOTAM's are transmitted on all Service A circuits, and stored in the Consolidated NOTAM System, after which they are entered in the Notices to Airmen Publication (NTAP), also referred to as the "Class II (mail distribution) publication" until canceled.
b. D NOTAM's issued under the Flight Service Stations' Accountability System receive the same dissemination as the surface weather report for the originating station, and provide the user with current information on an hourly basis. They are numbered to reflect the month of issuance and the sequence number of the month, (e.g. 6/18).
222. FDC NOTAM TYPES.
Changes to instrument flight procedures, which have been charted and distributed, may be processed as FDC NOTAM's and issued through NFDC. Procedural minimums shall not be lowered by NOTAM unless fully justified as a safety of flight issue. In order to identify procedural amendments that can be charted from the NOTAM information, AVN-100 personnel shall prefix the text with an action code as follows:
a. FI/P (Flight Information/Permanent). This prefix shall be used when the amended procedure is expected to be effective for more than 4 charting cycles (224 days). FI/P-NOTAM's (P-NOTAM's) contain information that is complete for charting purposes. Cartographic agencies will initiate immediate changes to charted information, based upon the P-NOTAM data, prior to receiving from NFDC the formal amendment to the appropriate procedure. Only one SIAP shall be addressed per P-NOTAM. P-NOTAM's may NOT be used for Airway changes. Refer to paragraphs 224b, c, and d for DP and STAR NOTAM procedures.
FI/P-NOTAM's may be used to amend procedures without a complete review of the procedure. The amendment will be indicated by an alphanumeric identifier; e.g., Amdt 3A, Amdt 4C, etc. A hard copy of each P-NOTAM shall be affixed to the current amendment and maintained in the procedures file by both the NFDC and AVN-100, for each SIAP until the next full amendment is effective.
b. FI/T (Flight Information/Temporary). Use this prefix when the amended procedure will be effective for less than 4 charting cycles (224 days). If, at any time, it is determined that the condition is expected to last longer or will become permanent, amend the procedure via an FI/P-NOTAM or revised 8260-series form. The P-NOTAM or 8260-series form should be submitted prior to the expiration of the temporary timeframe.
223. FDC NOTAM PREPARATION, REVIEW AND TRANSMITTAL.
a. AVN-100 is responsible for formulating procedural and airway FDC NOTAM's and forwarding them for transmittal. The following procedures apply:
(1) Coordinate all FDC NOTAM's with the affected ARTCC facility and the appropriate regional offices at the time of submission, or if unable, during the next normal workday (See also Order 8260.3, paragraph 150). Normally, AVN-100 should also notify the airport manager at the affected location.
NOTE: The ARTCC will ensure that the NOTAM's are forwarded to all affected ATC facilities under Order 7930.2F, paragraph 2-2-3.
(2) AVN-100 shall estabłish procedures to ensure that all NOTAM's are reviewed for accuracy, completeness, content, etc. prior to submission.
(3) Call NFDC to ensure a specialist is available to receive the NOTAM Once assured, submit NOTAM's to the NFDC via facsimile (FAX). A typewritten or legible handwritten copy is required; however, a telephone call is acceptable in emergencies. A record of a successful FAX transmittal after the phone call assures receipt.
(4) During periods when NFDC is closed or a specialist cannot be contacted, FAX the NOTAM directly to the USNOF. The NOTAM originator is responsible for ensuring USNOF receipt.
(5) Ensure that a copy of all FDC NOTAM's sent directly to the USNOF is clearly annotated that it has been sent directly to the USNOF and also sent to NFDC via FAX at the time of transmittal. This will preclude duplication and confusion.
b. NFDC is responsible for reviewing applicable FDC NOTAM's for accuracy, format, completeness, and data base agreement prior to forwarding them to the USNOF for transmittal. Discrepancies noted by NFDC will be resolved through the originating AVN-100 branch. NFDC is also responsible for compiling NOTAM's for inclusion in the Notices to Airmen Publication (NTAP) and follow up actions noted in paragraph 227.
c. The USNOF is also responsible for ensuring that FDC NOTAM's are in the proper format under this directive and Order 7930.2. Questions/ discrepancies will be addressed to the submitting agency, NFDC, or AVN-160 as appropriate. FDC NOTAM's affecting FAA developed military SIAP's
at civil locations shall be issued separately and forwarded to the USNOF military representative.
d. Cartographic Standards Branch, ATA-130, is responsible for issuing, tracking, and canceling FDC NOTAM's used to correct/amend U.S. government IFR en route and VFR sectional aeronautical charts when necessary to resolve charting errors.
224. INSTRUMENT PROCEDURE NOTAM's.
a. 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 workload, staffing level, etc. P-NOTAM's have proven to be an effective means of updating aeronautical charts within the following guidelines:
(1) There is no age limit on a SIAP submitted for P-NOTAM amendment as long as AVN-100 reviews it and ascertains that there are no other safety of flight changes required to the procedure. Do NOT prepare a NOTAM solely to address minor non-safety related discrepancies to a SIAP; however, if a NOTAM is required for safety reasons, other items may be included in the P-NOTAM to simultaneously update procedure charts.
(2) AVN-100 may issue P-NOTAM's for consecutive amendments to the same procedure. All P-NOTAM amendments shall be sequentially lettered (e.g., Amendment 13A, 13B, 13C, etc.) as a suffix to the current amendment.
(3) Exercise caution in adding P-NOTAM's to a procedure or when initiating a P-NOTAM when there is a current T-NOTAM in effect for the procedure. In many cases close follow-up action, including canceling and reissuing NOTAM's, will be necessary to ensure there is no confusion for pilots and chart producers.
Examples:
The currently published SIAP is AMDT 3. There is a T-NOTAM in effect for AMDT 3 that will remain in effect after AMDT 3A is charted. When AMDT 3A is charted, the T-NOTAM must be canceled and reissued for AMDT 3A.
The currently published SIAP is AMDT 4A. A P-NOTAM has been issued, but not yet charted promulgating AMDT 4B. Another P-NOTAM is required that will promulgate AMDT 4C. In this case, because AMDT 4B is not yet charted, issue a T-NOTAM against the currently charted procedure (AMDT 4A). When AMDT 4B is charted, cancel the T-NOTAM and reissue it as a P-NOTAM promulgating AMDT 4C.
(4) Issue a T-NOTAM and amend the SIAP as a priority to the AVN-100 work schedule, when all changes and corrections cannot be accommodated using a P-NOTAM.
(5) When changes to civil procedures also affect FAA-developed military procedures at civil or joint-use airfields, AVN-100 shall issue a separate FDC 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. AVN-100 shall request the USNOF to forward the civil NOTAM and the reason to the cognizant military authority for appropriate military NOTAM action.
(6) NOTAM requirements for FAA developed U.S. Army procedures at military airfields will be processed under Order 8260.15.
b. Changes to textual DP's shall be issued under the FDC NOTAM process as outlined under paragraph 223. Only FI/T-NOTAM's may be issued. Permanent procedural changes to textual DP's must be made via a new or amended Form 8260-15A within 224 days of the issuance of the associated NOTAM.
c. Changes to graphic DP's (formerly SID's) shall be promulgated as NOTAM (D)'s under Order 7930.2. These NOTAM's are developed by AVN-100 and are issued by the USNOF using the accountability code “USD." The following format examples are provided:
USD 12/001SAN 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
USD XX/XXX LAX CHATY TWO DEPARTURE, GORMAN TRANSITION: MINIMUM
ALTITUDE BROWS, INT TO GMN VORTAC, 8000 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.
(1) The following procedures shall be followed when a NOTAM (D) for a DP is required:
(a) AVN-100 shall forward the NOTAM text directly to the USNOF via facsimile for transmittal.
(b) For multiple airport DP's, a separate NOTAM (D) must be prepared for each airport affected by the DP.
(c) Temporary and permanent conditions may be promulgated via the NOTAM (D) process; however, NOTAM (D)'s shall not be used as a source to effect charting changes. Permanent procedural changes to graphic DP's must be made via a new or amended FAA Form 8260-15B within 224 days of the issuance of the associated NOTAM (D).
(d) The USNOF shall review each NOTAM to ensure formatting, contractions, etc. are correct and assign the NOTAM number. Questionable items must be resolved with the originator prior to issuance.
(e) Once issued, AVN-100 shall be responsible for obtaining the NOTAM number from the USNOF, tracking, and canceling the NOTAM when the condition requiring the NOTAM is no longer applicable.
d. Changes to STAR's requiring NOTAM action are also promulgated as NOTAM (D)'s. The appropriate ARTCC retains the responsibility for initiating, tracking, and canceling NOTAM (D)'s for STAR's.
e. General NOTAM (D) Actions.
(1) When a NOTAM (D) is issued closing an airport permanently, an FDC NOTAM need not be issued denying use of a SLAP. A routine procedure cancellation should be processed.
(2) When a NOTAM (D) is issued to shut down a facility permanently, only routine cancellation of procedures predicated on that facility are required. FDC NOTAM's may be required for other procedures supported by the affected facility.
(3) 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, inciuding takeoff/departure procedures, shall be processed.
(4) When a NOTAM (D) is issued for a facility shutdown or outage, an FDC NOTAM denying SIAP use is not required for those SIAP's using only that facility. However, other SIAP's in the vicinity must be reviewed to determine if that facility supports courses or fixes; in such cases, those SIAP's require an FDC NOTAM. Particular attention must be given to fixes supporting stepdown minimums and missed approach procedures which are predicated on the outof-service facility. It is not necessary to issue NOTAM's for fixes and terminal route segments which are related to unusable airway segments from the subject facility. Do not issue “"Radar Required" NOTAM's on unusable or restricted airway segments (see also paragraph 463).
When an instrument approach procedure is NOTAMed for an outage of an NDB or DME facility providing ancillary support, (not providing final approach course guidance), exempt aircraft equipped with IFR GPS systems from the restriction. For clarification, state the reason for the restriction in the text of the NOTAM. An example for use when a DME antenna is out of service: ‘DME MINIMUMS NA EXCEPT FOR IFR GPS-EQUIPPED AIRCRAFT, ORD DME OTS." An example of an ILS approach that uses an LOM for procedure entry and/or missed approach clearance limit: 'PROCEDURE NA EXCEPT FOR IFR GPS-EQUIPPED AIRCRAFT, FOR LOM OTS."
(5) 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.
(6) When radio control of approach lights or runway lights is commissioned or the frequency is changed, Flight Inspection issues a NOTAM (D) in accordance with Order 8200.1, United States Standard Flight Inspection Manual.
225. AIRWAY NOTAM's.
When a restriction or a change to an airway requires a NOTAM, forward an FDC T-NOTAM to NFDC following the procedures in paragraph 223. NOTAM's, reflecting airway changes within one or more ARTCC's airspace, are issued under the affected ARTCC identifier as Center Area NOTAM (CAN) FDC NOTAM's on the NOTAM circuit.
a. Airway changes involving a single state and one or more ARTCC's shall be issued with the ARTCC identifier followed by the two-letter state code. The two-letter state code must also follow all NAVAID and fix designators.
Example:
“FDC 8/0001 ZFW OK FI/T AIRWAY ZFW ZKC. V140 SAYRE (SYO) VORTAC, OK TO TULSA (TUL) VORTAC, OK MEA 4300.
FDC 8/0002 ZKC OK FI/T AIRWAY ZFW ZKC. V140 SAYRE (SYO) VORTAC, OK TO TULSA (TUL) VORTAC, OK MEA 4300.
REASON: TEMPORARY NEW TOWER. OE 98-ASW-0123."
REASON: TEMPORARY NEW TOWER. OE 98-ASW-0123."
b. If the airway NOTAM affects one but less than four ARTCC's and multiple states, issue one NOTAM for each affected ARTCC. If the NOTAM affects four or more ARTCC's, send one NOTAM using FDC as the facility identifier.
c. If the restriction will exceed the time limit established in paragraph 222b, forward an updated FAA Form 8260-16 and/or 8260-2 simultaneously to NFDC for charting.
Examples:
One ARTCC:
"FDC 8/0011 ZBW CT FI/T AIRWAY ZBW. V1 HARTFORD (HFD) VORTAC, CT TO MADISON (MAD) VOR/DME, CT MEA 3000.
REASON: TEMPORARY NEW TOWER. OE 98-ANE-1329."
REASON: TEMPORARY NEW TOWER. OE 98-ANE-1329."
Two ARTCC's:
"FDC 8/0011 ZBW FI/T AIRWAY ZBW ZNY. V1 HARTFORD (HFD) VORTAC, CT TO DIXIE INT, NJ MEA 3000.
FDC 8/0012 ZNY FI/T AIRWAY ZBW ZNY. V1 HARTFORD (HFD) VORTAC, CT TO DIXIE INT, NJ MEA 3000.
REASON: TEMPORARY NEW TOWER. OE 98-ANE-1329."
Three ARTCC's:
"FDC 8/0011 ZBW FI/T AIRWAY ZBW ZNY ZDC. V1 HARTFORD (HFD) VORTAC, CT TO WATERLOO (ATR) VORTAC, DE MEA 3000.
FDC 8/0012 ZNY FI/T AIRWAY ZBW ZNY ZDC. V1 HARTFORD (HFD) VORTAC, CT TO WATERLOO (ATR) VORTAC, DE MEA 3000.
FDC 8/0013 ZDC FI/T AIRWAY ZBW ZNY ZDC. V1 HARTFORD (HFD) VORTAC, CT TO WATERLOO (ATR) VORTAC, DE MEA 3000.
REASON: TEMPORARY NEW TOWER. OE 98-ANE-1329."
Four or more ARTCC's:
"FDC 8/0001 FDC FI/T AIRWAY ZNY ZDC ZAT ZJX. V1 DIXIE INT, NJ TO CRAIG (CRG) VORTAC, FL MEA 4000.
REASON: TEMPORARY NEW TOWER. OE 98-ANE-1329."
226. NOTAM CONTENT.
a. FDC NOTAM's shall identify the procedure being amended and the current amendment number. The NOTAM shall be as concise as possible, and shall 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 do not affect visibility minimums, do not require NOTAM action.
b. The text shall be prepared by AVN-100 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 which 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 FAA 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. If the NOTAM contains permanent information for charting, the last line of the NOTAM text shall identify it as the next sequential alphanumeric amendment; i.e., ORIG A, AMDT 4B, etc. The date of the NOTAM will become the effective date of that amendment.
e. 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.
Examples:
"FDC &/ ELP FI/P EL PASO INTL ARPT, EL PASO, TX. ILS RWY 22 AMDT 10... GS 3.0 DEGREES, TCH 51, GS ALT AT LOM 5155, GS ALT AT MM 4159. THIS IS ILS RWY 22 AMDT 10A.
Continue reading ↓ 120 of 373 passages shown