Order 8260.19E Flight Procedures and Airspace
This document is cancelled. Cancelled by 8260.19F. Check the official source before relying on it.
Change 8260.19E FEDERAL AVIATION ADMINISTRATION U.S. DEPARTMENT OF TRANSPORTATION
CHG 3
Effective Date: National Policy 02/22/2013
SUBJ: Flight Procedures and Airspace
1. Purpose. This order provides guidance to all FAA personnel for the administration and accomplishment of the FAA Flight Procedures and Airspace Program. 2. Audience. The primary audience for this Order is the Air Traffic Organization (ATO), Mission Support Services (MSS), Aeronautical Navigation Products Office (AeroNav Products), who has the responsibility to develop instrument flight procedures. The secondary audience includes the ATO MSS Aeronautical Information Management (AIM) Office (AJV-2), ATO Service Areas' Operational Support Group, Flight Procedures Team (OSG-FPT), Air Traffic’s Technical Operations Flight Inspection Services (AJW-3); Flight Standards headquarters, and regional office Divisions/Branches. 3. Where You Can Find This Change. You can find this order on the Directives Management System (DMS) Website: http://www.faa.gov/regulations_policies/orders_notices.
4. Explanation of Changes. Significant areas of new direction, guidance, policy, and criteria as follows:
a. General. All example NOTAMs updated to reflect new formatting requirements. Office names updated to current structure.
b. Table of Contents. Updates Table of Contents to coincide with the pages changed.
c. Chapter 1.
(1) Note Added. Added a Note to explain that all the responsibilities identified in this section are for information only and are there to assist procedure developers in knowing whom to contact for information in the performance of their duties.
(2) Paragraph 1-11b & 11g. Replaced reference to Form 8260-10 with Form 8260-7B that is the current Form used to issue Special instrument procedures.
(3) Paragraph 1-12b(1). Editorial.
(4) Paragraph 1-12b(6). Inserted “and instrument flight operations.”
Distribution: Electronic Only Initiated By: AFS-400
(5) Paragraph 1-14b(2). Added responsibility to develop and maintenance Diverse Vector Areas (DVAs).
d. Chapter 2.
(1) Figures 2-1 through 2-3. Titles and drawings edited to correctly display base of cylinders.
(2) Paragraph 2-17a(8). Editorial change at the request of AeroNav Products.
(3) Paragraph 2-18a. At the request of AeroNav Products, added requirement for RAPT approval to make changes.
(4) Paragraph 2-18a Note (added). Add note with guidance for locations that have a rapid rate of magnetic variation change.
(5) Paragraph 2-18d. Change “bearing” to “heading” to be consistent with IACC 4, paragraph 3.6.2.2.1.4.
(6) Paragraph 2-18f(1)(b). Editorial change for clarity.
(7) Paragraph 2-22. Clarifies that both temporary and permanent conditions may be promulgated via FDC NOTAM. Note added to discontinue use of “FI/T” and “FI/P” designations.
(8) Paragraph 2-22a. Mandates use of “EST” following the date/time group to indicate the NOTAM is for a temporary condition.
(9) Paragraph 2-22a(2). Added requirement to send a copy of correspondence to AFS-460. Changed from requiring a “waiver” to obtaining “Flight Standards approval.” Clarified that FDC NOTAMs relating IFPs must not be canceled and re-issued.
(10) Paragraph 2-22b. Mandates use of “PERM” in lieu of an expiration date/time group to indicate the NOTAM is for a temporary condition.
(11) Paragraph 2-22b(3). Clarifies that a single P-NOTAM can be used to address the same government charting error(s) for multiple procedures. Clarifies those exceptions when a P-NOTAM may be used to address more than one procedure.
(12) Paragraph 2-22b(7). Provides an exception to exceed 150 P-NOTAMs and coordination action required. Clarifies exceptions to the 150 P-NOTAM limitations per AIRAC cycle and adds requirements to coordinate with civil charting agents when the limitation will be exceeded.
(13) Paragraph 2-23a. Specified that the key word must follow the location identifier.
(14) Paragraph 2-23b. New paragraph added to mandate that a 10-digit effective time and expiration time be added as the last item in the FDC NOTAM text. Provides guidance for both temporary and permanent conditions. Eliminates the use of “WIE,” “UFN,” “TIL,” and “WEF” to indicate NOTAM times.
(15) Paragraph 2-23c. Clarifies NOTAM responsibilities for IFPs developed under a Service Provider agreement.
(16) Paragraph 2-29b. Editorial change using plain language.
(17) Paragraph 2-41a(2). Revised second sentence for clarity.
(18) Paragraph 2-63a(3) and (5). Changed “Other Transactional Authority” to “Service Provider.”
(19) Paragraph 2-74c(3)(b)3. Removed unnecessary text.
(20) Paragraph 2-75. Removed “Vertical” from paragraph description since the paragraph addresses both vertical and horizontal datums.
(21) Section 12. Added “Approval Requests” to title.
(22) Paragraphs 2-80 and 2-81. Paragraphs expanded to address waivers and Flight Standards Service approval requests. Guidance to clarify that instrument flight procedures must not be submitted for publication until all waiver and/or approval request action has been completed. Additionally, paragraphs were re-sequenced to provide a sense of the process flow.
e. Chapter 4.
(1) Section 4. Special Instrument Procedures Processing removed and consolidated into a separate Order.
(2) Paragraph 4-6i(1). Added sentence to clarify that sidestep procedure visibilities must not be less than 1 mile for CAT A-B and not less than 1½ for CAT C-E.
(3) Paragraph 4-7i(1). Removed reference to Table 3-11; table was removed from Order 8260.3B, Volume 1, Chapter 3, with Change 23.
(4) Paragraph 4-60b. Removed reference to CAT IIIc.
(5) Paragraph 4-61b(1)(e). Removed reference to CAT IIIa/b/c.
(6) Paragraph 4-61b(2). Removed reference to CAT IIIa/b/c.
(7) Paragraph 4-61c. Updated guidance at the request of Flight Inspection Services.
(8) Paragraph 4-71 (Added). Added guidance for DVA.
(9) Paragraph 4-81b(6). Updated to correctly identify proper office for distribution.
(10) Paragraph 4-91e. Removed reference to “MLS” and added “LOC” and added a note for clarity.
(11) Paragraph 4-91e(3) and (4). Removed and guidance relocated to paragraphs 8 55h(4) and (5).
(12) Paragraph 4-91e(5). Removed and guidance relocated to paragraph 8-51a(6).
(13) Paragraph 4-91f. Moved to paragraph 8-55h(6).
(14) Paragraph 4-94d. Revised paragraph for CA Leg application per AeroNav Products submitted recommendation.
(15) Paragraph 4-96. Expanded and clarified Baro-VNAV limitations based on a remote altimeter source.
(16) Paragraph 4-97. Editorial changes made to remove reference to Order 8260.3 and instead refer to current RNAV criteria standards. Editorial changes to define where to document information on the revised FAA Form 8260-9. Added requirement to document descent rate for standard and high temperature situations on FAA Form 8260-9. Deleted “Note” that was incorporated into Order 8260-58.
(17) Paragraph 4-98. Add reference to critical DME facilities.
(18) Paragraph 4-99j. Edit to allow standard charting icon for speed limitation when there is no ending point.
f. Chapter 5.
(1) Paragraph 5-2. Expanded responsibility and processing guidance.
(2) Paragraph 5-3. Expanded guidance pertaining to the review of notices.
(3) Paragraph 5-3c. Added reference to DVA.
(4) Paragraph 5-3h. Added text to last sentence saying: “After resolving any disagreement…”
(5) Figure 5-3. Corrected calculations.
(6) Paragraph 5-8c. Added guidance that Class B airspace must encompass all final approach fix minimum altitudes to include glideslope intercept altitudes.
(7) Paragraph 5-8c(4)(a)3. Added text for clarity.
(8) Paragraph 5-8e(2)(d)2. Added text for clarity.
(9) Paragraph 5-8e(3)(a)3. Added text for clarity.
g. Chapter 6. Paragraph 6-1c. Updated USN contact information.
h. Chapter 7.
(1) Paragraph 7-1c (Added). Moved from paragraph 8-1b.
(2) Paragraph 7-1d (Added). Moved from paragraph 8-1c.
i. Chapter 8.
(1) Paragraphs 8-1b & c. Moved to paragraphs 7-1c & d.
(2) Paragraph 8-3a. Added guidance for FAA Form use when the FAA is developing instrument procedures for the DoD.
(3) Paragraph 8-3b(1). Added TACAN.
(4) Paragraph 8-3b(2). Added Note to clarify that LDA with glideslope is not part of a procedure title, thus a part of an LDA or LDA/DME procedure.
(5) Paragraph 8-5. Deleted reference to Order JO 7910.2.
(6) Paragraph 8-6a. Corrected paragraph number reference and added an additional reference; paragraph 8-55g.
(7) Paragraph 8-6b. Added reference to paragraph 8-55g(2).
(8) Paragraph 8-6g(1). Added guidance for situations when NoPT annotation is permitted when arriving via a STAR.
(9) Paragraph 8-7g(5) Added. Added guidance on the application of arrival holding patterns.
(10) Paragraph 8-11c(4). Changed to limit “Hard Dates” to apply to only magnetic variation rotations ground navaid facilities.
(11) Paragraph 8-11e. Added reference to “Flight Inspection/validation official” where necessary.
(12) Paragraph 8-11g. Removed guidance on signature authority within AJV-3 and what the signature signifies at their request.
(13) Paragraph 8-11h. Moved some of the information removed from paragraph 8-11g to this paragraph.
(14) Paragraph 8-13a(4). Added “ground track” to end of sentence.
(15) Paragraph 8-13b(17). Add reference to CAT II/III/SA CAT II.
(16) Paragraph 8-13c. Editorial and added guidance for adding SA CAT I minimums to a procedure with an existing CAT II procedure to that runway.
(17) Paragraph 8-13e(1). Added text to be more explicit on intent.
(18) Table 8-1. Added “ground track” to text to match change to paragraph 8-13a(4). Deleted “X” in P-NOTAM column for paragraph 8-13b(5) when runway numbering is changed.
(19) Table 8-2. “Orig” change to “Electronic Copy” for Form 8260-2 NFDC copy.
(20) Paragraph 8-30e. Added text for clarity when establishing an equivalent level of safety.
(21) Paragraph 8-30h. Added “(paper/electronic)” to paragraph for waiver submissions.
(22) Figures 8-1 and 8-2. Text edited to move location identifier adjacent to airport name, dates added, and title block edited.
(23) Paragraph 8-40a. Added “holding” and requirement to inform a company that is maintaining a Part 97 procedure to last sentence.
(24) Paragraph 8-41g(3)(j). Added, at the request of Flight Inspection Services, the following Note: “When an MCA is assigned in order to meet flight check signal reception requirements, ensure the applicable facility MRA matches the MCA.”
(25) Paragraph 8-41h(2)(e) and (f). Added “magnetic” after “degree” for clarity.
(26) Paragraph 8-41s. Changed “associated with” to read “required by” for clarity.
(27) Paragraph 8-41t(4). Editorial and added the option to submit electronically.
(28) Paragraph 8-51a(6). Moved requirement from paragraph 4-91e(5) so that paragraph could be removed.
(29) Paragraph 8-51b. Added “or other charting authority” after AeroNav Products in last sentence.
(30) Paragraph 8-52b. Editorial corrections placing commas in correct locations, added a DME distance to one example, and removed “ft” abbreviation where ever used.
(31) Paragraph 8-52b(3). Editorial - Added sample form entry back into paragraph.
(32) Paragraph 8-52e(1). Editorial - Removed “or circling.”
(33) Paragraph 8-52e(2). Added guidance for SA CAT I procedures that have a 150-ft HAT/HATh.
(34) Paragraph 8-52h(1). Deleted “When the MSA facility is an LOM, enter only the identification and type of facility.”
(35) Paragraph 8-53b(6). Removed reference for MLS and editorial correction.
(36) Paragraph 8-54e. Changed to refer to Order 8260.3 for guidance for selecting category of minimums to publish.
(37) Paragraph 8-54g(2). Added guidance to clarify that an LP procedure will not be established in conjunction with an LNAV/VNAV procedure on the same chart.
(38) Paragraph 8-54i(1). Added guidance regarding placement of an attention symbol.
(39) Paragraph 8-54k(5). Removed references to CAT III “a/b/c.”
(40) Paragraph 8-54m(6). Add autoland chart note restriction for GLS procedures.
(41) Paragraph 8-54m(7)(a) and (b). Added “GLS.”
(42) Paragraph 8-54m(7)(c). Editorial.
(43) Paragraph 8-55b. Added examples of notes not to be specified on instrument procedure charts.
(44) Paragraph 8-55e(8). Removed LNAV/VNAV glidepath angle and precipitous terrain limitations because they are specified in criteria in the most current 8260-series Orders.
(45) Paragraph 8-55f. Editorial changes to include replacing “Service A” with “Weather Message Switching Center Replacement (WMSCR).”
(46) Paragraph 8-55g. Added “GPS” due to the ATO lifting the requirement to have radar monitoring on aircraft operating on random (impromptu) RNAV routes when using GPS.
(47) Paragraph 8-55h(4), (5), and (6) Added. Moved guidance from paragraphs 4-91e(3)&(4) and 4-91f, as it is more appropriate to appear in this paragraph that supports “Equipment Requirement Notes.”
(48) Paragraph 8-55m(5). Added text to clarify that a speed greater than 90 KIAS is permitted.
(49) Paragraph 8-55m(6). Edited text to accommodate removing “nonstandard” in order to disassociate this term with “climb gradient.”
(50) Paragraph 8-55s(5). Paragraph deleted.
(51) Paragraph 8-56c. Added example for LP.
(52) Paragraph 8-56d(9). Added provision to allow less “detailed” RNAV missed approach instructions due to them being coded in the aircraft database.
(53) Paragraph 8-56e. Edited text to accommodate removing “nonstandard” in order to disassociate this term with “climb gradient.”
(54) Paragraph 8-56e(1) Examples. Removed “Circling.”
(55) Paragraph 8-56e(2). Editorial to clarify these conditions are to be applied to the same type of minima.
(56) Paragraph 8-57k. Removed requirement to depict an adjacent localizer on the chart where simultaneous approaches are authorized (See Aeronautical Charting Forum, Charting Group, Agenda Item 12-02-258).
(57) Paragraph 8-57t. Clarified that Flight Standards approval from AFS-400, through AFS-460, is required for maximum or mandatory altitudes in the final or missed approach segment. Additionally, a second Note was added to clarify that a waiver would also be required when applying these restrictions to a missed approach segment.
(58) Paragraph 8-57u. Deleted sentence no longer needed. Incorporated the “Note” into the basic paragraph and added a sentence to permit not publishing a VDA when Flight Inspection has identified a safety issue when aircraft continue on the VDA path below the MDA.
(59) Paragraph 8-57aa. Added guidance for adding secondary airports to plan/profile views on an instrument approach chart.
(60) Paragraphs 8-60 thru 8-69. Revised paragraphs to support adoption of revised Form 8260-9, report format.
(61) Paragraph 8-60a(3)(a). Add guidance on when DA would be added to “ELEV” block.
(62) Paragraph 8-60b(16). Last sentence, added HAL to accommodate helicopter procedures.
(63) Paragraph 8-80c(1). Editorial change made to match text in Order JO 7400.2J, paragraph 20-1-5d.
j. Appendix A. Added forms reference to include FAA Forms 8260-15D and 8260-15E.
k. Appendix B.
(1) Revised header language to indicate that all the publications listed within this appendix is provided for information purposes and may not be a complete listing.
(2) Updated references.
l. Appendix C.
(1) Paragraph 2b(2)i2. Editorial change and corrected paragraph reference.
(2) Paragraph 2b(3)b. Corrected paragraph reference.
m. Appendix J. Sample forms updated.
n. Appendix K. Sample form for FAS Data Block updated with datum references.
o. Appendix L.
(1) General. Where ever “WGS-84” is mentioned, “/NAD83” was added immediately following it. It has been determined that geographical coordinates in the NAD83 datum is an acceptable value to use in FAS Data Block calculations under specific circumstances as defined in other FAA policy directives/memorandums.
(2) Paragraph 4d. Editorial change to update to current standards and added guidance for WAAS circling only.
(3) Paragraph 4i. Added sentence to indicate that “Reference Path Identifier” is Michael Zenkovich, signing for AFS-1
PAGE CONTROL CHART
Remove Pages Dated Insert Pages Dated
i thru xii 03/21/12 i thru xii 02/22/13
1-1 thru 1-14 03/21/12 1-1 thru 1-14 02/22/13
2-7 thru 2-8 06/21/11 2-7 thru 2-8 02/22/13
2-13 thru 2-14 03/21/12 2-13 thru 2-14 02/22/13
2-17 thru 2-36 03/21/12 2-17 thru 2-36 02/22/13
2-37 thru 2-38 06/21/11 2-37 thru 2-38 02/22/13
2-39 thru 2-56 03/21/12 2-39 thru 2-56 02/22/13
4-7 thru 4-10 03/21/12 4-7 thru 4-10 02/22/13
4-13 thru 4-26 03/21/12 4-13 thru 4-26 02/22/13
4-27 thru 4-28 03/21/12 4-27 thru 4-28 02/22/13
4-29 thru 4-30 06/21/11 4-29 thru 4-30 02/22/13
4-31 thru 4-34 03/21/12
4-35 thru 4-36 06/21/11
4-37 thru 4-44 03/21/12
5-1 thru 5-6 03/21/12 5-1 thru 5-6 02/22/13
5-7 thru 5-26 06/21/11 5-7 thru 5-26 02/22/13
5-27 thru 5-38 03/21/12 5-27 thru 5-40 02/22/13
6-1 thru 6-2 08/25/10 6-1 thru 6-2 02/22/13
7-1 thru 7-8 08/25/10 7-1 thru 7-8 02/22/13
7-13 thru 7-14 08/25/10 7-13 thru 7-16 02/22/13
8-3 thru 8-124 03/21/12 8-3 thru 8-126 02/22/13
A-5 thru A-6 06/21/11 A-5 thru A-6 02/22/13
B-1 thru B-4 03/21/12 B-1 thru B-4 02/22/13
C-3 thru C-6 08/25/10 C-3 thru C-6 02/22/13
D-1 thru D-2 03/21/12 D-1 thru D-2 02/22/13
J-3 thru J-12 03/21/12 J-3 thru J-60 02/22/13
K-3 thru K-4 03/21/12 K-3 thru K-4 02/22/13
L-1 thru L-8 06/21/11 L-1 thru L-8 02/22/13
CHG 2
Change 8260.19E FEDERAL AVIATION ADMINISTRATION U.S. DEPARTMENT OF TRANSPORTATION
CHG 2
Effective Date: National Policy 03/21/2012
SUBJ: Flight Procedures and Airspace
1. Purpose. This order provides guidance to all FAA personnel for the administration and accomplishment of the FAA Flight Procedures and Airspace Program.
2. Audience. The primary audience for this Order is the Air Traffic Organization (ATO), Mission Support Services (MSS), Aeronautical Navigation Products Office (AeroNav Products), who has the responsibility to develop instrument flight procedures. The secondary audience includes the ATO MSS Aeronautical Information Management (AIM) Office (AJV-2), ATO Service Areas' Operational Support Group, Flight Procedures Team (OSG-FPT), Air Traffic’s Technical Operations Aviation System Standards Office (AJW-3); Flight Standards headquarters, and regional office Divisions/Branches.
3. Where You Can Find This Change. You can find this order on the Directives Management System (DMS) Website: http://www.faa.gov/regulations_policies/orders_notices.
4. Effective Date. March 21, 2012.
5. Explanation of Changes. Significant areas of new direction, guidance, policy, and criteria as follows:
a. General. Changed “AeroNav Services” to “AeroNav Products” throughout this Order.
b. Table of Contents. Updates Table of Contents to coincide with the pages changed.
c. Chapter 1.
(1) Paragraph 1-12. Updated to show Regional NextGen Branch (RNGB) responsibilities.
(2) Paragraph 1-14a(1). NFDC responsibilities updated.
(3) Paragraph 1-14a(2). Paragraph added to outline responsibilities of the Geographic Services Group as they relate to gathering validating, and maintaining data used for IFP development.
(4) Paragraph 1-22c. Change Aviation System Standards Information System (AVNIS) to AIRNAV database, here and throughout this Order.
Distribution: Electronic Only Initiated By: AFS-400
d. Chapter 2.
(1) Paragraph 2-12. Revised to prevent use of a localizer for lateral guidance that makes up an airway and allows use only as a crossing facility to define a fix on an airway. Sub-paragraph c deleted.
(2) Paragraph 2-14c(2). Deleted. Guidance relocated to Order 8260.3, Volume 1, paragraph 3.4.2. Sub-paragraphs re-numbered.
(3) Paragraph 2-16a. Editorial clarification and added the following information statement: “It should also be noted that there is a problem that persists in characterizing magnetic declination when airborne equipment (RNAV) applies the magnetic variation from the local NAVAID or computes the magnetic variation dynamically and applies it to a computed course or desired track.”
(4) Paragraph 2-16b. Deleted Technical Operations Aviation System Standards as a participating office and added Service Area OSG-FPTs.
(5) Paragraph 2-17a. Revised AeroNav Products responsibilities per recent reorganization to included other editorial changes for clarity.
(6) Paragraph 2-17e. Removed paragraph 2-17e, Airports, and consolidated part into the updated paragraph for “Regional Airports/Airports District Office (ADO).
(7) Paragraph 2-18a. Split out and better defined MV requirements for CAT II/III procedures.
(8) Paragraph 2-18f(1). Editorial.
(9) Paragraph 2-18f(2). Editorial and split into 3 sub-paragraphs.
(10) Paragraph 2-22b. Clarified that P-NOTAMs may be used to substitute for the abbreviated amendment process within limitations.
(11) Paragraph 2-26e. Changed all examples with “OTS” to read “OUT OF SERVICE” per forthcoming change in Order JO 7930.2M.
(12) Paragraph 2-29e. Changed “Biennial” to “Periodic.”
(13) Paragraph 2-40. Clarified guidance regarding action to be taken when new/revised criteria and policy affect an instrument procedure.
(14) Paragraph 2-40b. Added guidance on what date should be used to determine when a periodic review is required. Subsequent paragraphs up-lettered.
(15) Paragraph 2-40d. Added more specific guidance on what information must be provided when documenting the periodic review and an example of what this might look like.
(16) Paragraph 2-41. Changed “AeroNav Products Action” to “Reviewing Organization Action” to cover other organizations that could be responsible for conducting the periodic review.
(17) Paragraph 2-41a(8). Editorial and added requirement for FPT to receive a copy of the documentation specified in paragraph 2-40d.
(18) Paragraph 2-63a. Added guidance to define initiating, maintaining, and transferring responsibilities for Form 8260-2.
(19) Paragraph 2-64a(8). Added guidance on what makes up a CNF name.
(20) Paragraph 2-71a. Paragraph revised to reflect the Geographic Services Group as office of primary responsibility for obstacle data vice the AeroNav Products Office.
(21) Paragraph 2-71b. Deleted reference to using best available source, changing to a statement that says “Lack of survey data may not permit lowest possible minima.”
(22) Paragraph 2-72b(1) through (5). Added reference to applicable corresponding accuracy code.
(23) Paragraph 2-72b(6). Deleted “See exception in paragraph 2-74b(3)(a).”
(24) Paragraph 2-73. Added sentence stating accuracy code adjustments are not applied to tethered balloons when defined by a Restricted Area boundary.
(25) Paragraph 2-73c. Corrected paragraph reference.
(26) Paragraph 2-74c(3)(a). Deleted reference to “transitional surface.”
(27) Paragraph 2-75b. Changed “GNSS” to read “Ground Based Augmentation System (GBAS).”
(28) Paragraph 2-84. Added guidance on conducting a review of the waiver(s) at the same time when the periodic review is being conducted.
e. Chapter 3. Paragraph 3-72. Deleted “…AeroNav Products review must assume that both obstacle clearance and controlled airspace requirements are met for MVAs and MIAs” due to conflicting requirement stated in paragraph 3-73a(2).
f. Chapter 4.
(1) Paragraph 4-3b. Paragraph split to clarify guidance.
(2) Paragraph 4-3c. This is a new paragraph taking portions of the old paragraph 4-3b and added guidance stating the no less than 700-ft Class E airspace must be in place prior to establishing an instrument procedure.
(3) Paragraph 4-3d. Added new paragraph to clarify that “minor adjustments” may only applied to existing Class E airspace. Remaining paragraph re-numbered.
(4) Paragraph 4-3e(1). Last sentence, changed “will” to “may.”
(5) Paragraph 4-3e(2). Added “will be identified by the DoD” to the end of the second sentence.
(6) Paragraph 4-5v. Deleted. Guidance added to Order 8260.3B, Vol. 1, Chapter 3.
(7) Paragraph 4-6h. Paragraph reference changed.
(8) Chapter 4, Section 4. Throughout this section, editorial changes were made where it was appropriate to use “proponent/operator” and “agent hired by the proponent or operator.” Also the term “submitter” was used where appropriate.
(9) Paragraph 4-41b(13). Added paragraph RNGB responsibility regarding NOTAM action when notified by non-FAA service provider responsible for maintaining a Special instrument procedure.
(10) Paragraph 4-41c(1). Editorial.
(11) Paragraph 4-41c(9). Added guidance on what a procedure package consists of.
(12) Paragraph 4-41d(5). Added: Provide Flight Inspection Results via Flight Inspection Procedure Control Form 8200-6-1.
(13) Paragraph 4-42b. Added “original and amendments” to the first sentence and added a third Note requiring procedure packages to contain proper Form 8260-2 documentation.
(14) Paragraph 4-43. Revised guidance to support changes being made in the procedure amendment process.
(15) Paragraph 4-52b. Changed paragraph reference.
(16) Paragraph 4-91f Added. Added paragraph to require a note be charted on GLS procedures that indicates “GPS Required.”
(17) Paragraph 4-99a. Deleted sentence requiring LAAS channel numbers for each IAF.
g. Chapter 5.
(1) Paragraph 5-3c. Added text at the end of the paragraph that requires documentation indicate IFR effect when there is a penetration of the visual area obstacle clearance surfaces.
(2) Paragraph 5-3c Note (Added). Added note to describe meaning of “proposed” instrument approach/departure procedure.
(3) Paragraph 5-8h(1)(a). Added statement “(or presumed IF per TERPS)” to cover situations where procedure turns are involved and the Intermediate Fix is not formally defined with a fix name.
(4) Paragraph 5-9c. Changed AeroNav Services to Service Area OSG-FPT.
(5) Paragraph 5-17b. Added text to clarify that the obstacle itself is not to be evaluated when the boundary of the Restricted Area is used to define the location of a tethered balloon.
(6) Paragraph 5-21. Changed AeroNav Services to Service Area OSG-FPT and deleted last sentence.
(7) Paragraph 5-22. Added OSG-FPT after Air Traffic Service Area.
h. Chapter 8.
(1) Paragraph 8-4a(4). Paragraph revised to refer to paragraph 2-18f(2).
(2) Paragraph 8-5b. Deleted “and where these data are not currently charted” to eliminate confusion and better define what is required.
(3) Paragraph 8-5b(3). Added “airport” and modified example to be more definitive.
(4) Paragraph 8-11a. Policy clarified to note that the “All Procedures Reviewed” block relates only to the procedures documented on the specific form being completed.
(5) Paragraph 8-11d. Changed ATA to Airlines for America (A4A) per their name change.
(6) Paragraph 8-11h. Modified to address procedures developed under the Other Transaction Agreement (OTA) having approval authority.
(7) Paragraph 8-13. Paragraph renamed to “Revisions to Instrument Flight Procedures (IFPs)” and expanded to include policy currently published in paragraphs 8-58e (1) through 8-58e (6) to more clearly breakout the amendment process. Also see paragraph 8-58e.
(8) Paragraph 8-13a(8). Subparagraph added to provide guidance when a runway is physically relocated.
(9) Paragraph 8-13b. Wording added to ensure harmonization with paragraph 8-11a. Subparagraphs added to clearly specify items that require a procedure amendment.
(10) Paragraph 8-13b(15). Note added to clarify policy for non-RNAV procedures.
(11) Paragraph 8-13b(15)(b). Distance changed to 0.1 NM or greater vice greater than 0.1 NM.
(12) Paragraph 8-13b(15)(c). Distance changed to 0.5 NM or greater vice greater than 0.5 NM
(13) Paragraph 8-13b(16). Clarified minimums changes and added requirement that adding a line of minima requires a procedure amendment.
(14) Paragraph 8-13b(20). Clarified that an amendment is required for changes to plan view, profile view, or briefing strip chart notes.
(15) Paragraph 8-13b(21). Added paragraph to allow changes to charted obstacles identified on the Form 8260-3/5, in the “Additional Flight Data” block be allowed by amendment.
(16) Paragraph 8-13c. Paragraph re-written to clarify what procedural changes may and may not be promulgated via an abbreviated amendment.
(17) Paragraph 8-13c(4). Example revised to delete contradiction
(18) Paragraph 8-13d(3). Clarified that no amendment is required when there are changes to “uncharted” obstacles.
(19) Paragraph 8-13d(5). Clarified that no amendment is required when fix coordinates are changed and the procedure chart and CRC remainder code are unchanged.
(20) Paragraph 8-13f. Paragraph revised to clarify chart changes that may be made without a procedure amendment.
(21) Paragraph 8-13g. Paragraph added to provide reference for changes to ODPs and SIDs.
(22) Table 8-1. New table added to provide a tool to assist in the application of the policy identified in paragraph 8-13. Current Table 8-1 changed to 8-2.
(23) Table 8-2. Added distribution requirements for Form 8260-15D.
(24) Paragraph 8-41b. Last sentence deleted that address using OA, OG, and OP for offshore fixes. See paragraph 8-41d.
(25) Paragraph 8-41d. Inserted new paragraph/guidance to use “ICAO REGION CODE” to support new FAA NextGen automation systems. All following paragraphs renumbered accordingly.
(26) Paragraph 8-41e(2). Added NDB to facilities example.
(27) Paragraph 8-41h(6)(b). Removed second and third sentence that was classified as holding pattern criteria and inappropriate for this paragraph.
(28) Paragraph 8-41i(2). Added requirement to enter assigned magnetic variation for when holding is over a ground-based Navaid.
(29) Paragraph 8-41r. Deleted “Developed by” and replaced it with “Office of Primary Responsibility.”
(30) Paragraph 8-41s. Revised “Approved By” guidance to address approval authorities.
(31) Paragraph 8-41q. Modified text to limit necessity.
(32) Paragraph 8-52f(4). Sentence modified to remove implication that there can be more than one glidepath intercept point defined on the chart.
(33) Paragraph 8-52g(2). Removed reference to Order 8240.47 and use of RDH/ARDH in lieu of TCH.
(34) Paragraph 8-53. Added reference to Order 8260.3.
(35) Paragraph 8-53b(1). Deleted. Guidance was added to Order 8260.3, Volume 1, paragraph 3.4.1. Following paragraphs renumbered accordingly.
(36) Paragraph 8-53b(3). Added guidance to place an “X” in the “NA” box when the instrument procedure only contain LPV minimums. Following paragraphs renumbered accordingly.
(37) Paragraph 8-54g(2). Added limitation defining when LP minimums will be provided.
(38) Paragraph 8-54i(3). Revised chart notes regarding helicopter visibility reductions.
(39) Paragraph 8-54m(2)(g). Added more “NA at night” restrictions to support recent changes to Order 8260.3B, Volume 1, Chapter 3, for the visual assessment area.
(40) Paragraph 8-54m(2)(h). Added requirement to obtain Flight Standards (AFS-400) approval prior to using a VGSI as a mitigation for 20:1 OIS penetrations in the visual assessment area and more “NA at night” restrictions.
(41) Paragraph 8-54m(7). Revised paragraph to show the “simultaneous” annotation is required when ATC has determined that an instrument procedure qualifies for either “dependent” or “independent” simultaneous operations. Removed sentence that states only vertically guided procedures are eligible for SIPIA operations. TERPS and/or ATC guidance stipulates equipment/operational requirements for “dependent” or “independent” simultaneous operations.
(42) Paragraph 8-54m(7)(a-d). Broke guidance out into 4 separate paragraphs. Expanded examples. Revised paragraph to show that the charted vertical guidance restrictions only apply to RNAV (GPS) procedures that contain LNAV minima on the same chart that contain LPV and/or LNAV/VNAV procedures. “LOC” restriction removed since ATC will clear aircraft for the LOC procedure only when a glideslope outage occurs.
(43) Paragraph 8-55a NOTE (Added). Note added to give flexibility to placement of chart notes when the chart is not produced by the FAA and it is for a Special instrument procedure.
(44) Paragraph 8-55e(3). Added Note to prohibit use of Automated UNICOM (AUNICOM) systems for IFR use.
(45) Paragraph 8-55e(9). Revised for clarity.
(46) Paragraph 8-55m(3) & (4). Removed set speed values and replaced with “XX” and added a note to subparagraph (4) providing an explanation about what speed values should be inserted.
(47) Paragraph 8-55n(2). Added “and/or TCH values” to be consistent with previous paragraph guidance.
(48) Paragraph 8-55r. Removed references to “RNAV.”
(49) Paragraph 8-56c(1). Added reference to FAA Form 8260-7A and added example for when Missed Approach Point is other than threshold.
(50) Paragraph 8-56c(2). Added reference to FAA Form 8260-7A.
(51) Paragraph 8-56d(4). Added requirement to document on Form 8260-9 the reason why “immediate” was used.
(52) Paragraph 8-56f. Added back in the statement that “Holding must be established at the clearance limit.” This was inadvertently removed with change 1.
(53) Paragraph 8-57b. Added example for “primary remote automated altimeter setting source.”
(54) Paragraph 8-57h(1). Added non-vertically guided offset procedures to the examples.
(55) Paragraph 8-57n(2). Modified guidance to refer to paragraph 2-18f(2) for all RNAV MagVar application.
(56) Paragraph 8-57n(3). Deleted. Guidance now addressed in paragraph 8-57n(2).
(57) Paragraph 8-57p. Removed requirement to list multiple landing areas for Special helicopter procedures that are annotated “Proceed Visually.”
(58) Paragraph 8-57z (Added). As discussed and agreed upon at Aeronautical Charting Forum 11-02, a Circling icon will be added to the chart to indicate that the new Order 8260.3B, Change 21, Circling criteria has been applied. Added a requirement to document in Additional Flight Data that this icon must be charted.
(59) Paragraph 8-58e. Paragraphs 8-58e(1) through 8-58e(6) re-located to paragraph 8-13.
(60) Paragraph 8-60a(4). Added reference to paragraph 8-60c(17).
(61) Paragraph 8-60a(5). Added guidance to show runway number as MSA center point for RNAV procedures that do not have a TAA.
(62) Paragraph 8-60c(6). Removed requirement to document Flight Inspection derived RDH/ADRH values. Renumbered following paragraphs.
(63) Paragraph 8-60c(17) (Added). As discussed and agreed upon at Aeronautical Charting Forum 11-02, added a requirement to document on Form 8260-9 that Order 8260.3B, Change 21, Circling criteria has been applied and the applicable radii.
(64) Paragraph 8-80i. Expanded guidance for documenting MTAs.
i. Appendix A. Deleted AVNIS and added GBAS and GLS to Acronyms and Abbreviations.
j. Appendix B. Updated text, Orders, and Advisory Circulars
k. Appendix D. Expanded instructions.
l. Appendix E. Added ICAO Region Code to all Form 8260-2, Radio Fix and Holding Data Record samples and made minor editorial changes where needed.
m. Appendix F. Revised sample 8260-3 fonn to correspond with guidance.
n. Appendix J. Revised sample 8260-9 fonns to correspond with guidance.
o. Appendix K. Revised sample 8260-10 fonns to correspond with guidance.
p. Appendix L.
(1) Paragraph 2r. Revised "Course Width at Threshold" to correspond with latest guidance from RTCA DO-229D requirements.
(2) Figure L-I. Updated to support changes made for documenting "Course Width at Threshold."
J ohn McGraw, signing
for AFS-1
PAGE CONTROL CHART
Remove Pages Dated
i thru xii 06/21/11 i thru xii 03/21/12
1-3 thru 1-12 06/21/11 1-3 thru 1-12 03/21/12
2-1 thru 2-4 06/21/11 2-1 thru 2-4 03/21/12
2-9 thru 2-36 06/21/11 2-9 thru 2-36 03/21/12
2-39 thru 2-56 06/21/11 2-39 thru 2-56 03/21/12
3-3 thru 3-14 08/25/10 3-3 thru 3-14 03/21/12
4-1 thru 4-10 06/21/11 4-1 thru 4-8 03/21/12
4-13 thru 4-28 06/21/11 4-13 thru 4-28 03/21/12
4-31 thru 4-34 06/21/11 4-31 thru 4-34 03/21/12
4-37 thru 4-44 06/21/11 4-37 thru 4-44 03/21/12
5-1 thru 5-6 06/21/11 5-1 thru 5-6 03/21/12
5-27 thru 5-38 06/21/11 5-27 thru 5-38 03/21/12
8-1 thru 8-118 06/21/11 8-1 thru 8-124 03/21/12
A-1 thru A-4 06/21/11 A-1 thru A-4 03/21/12
B-1 thru B-4 06/21/11 B-1 thru B-6 03/21/12
D-1 thru D-2 06/21/11 D-1 thru D-2 03/21/12
E-3 thru E-12 08/25/10 E-5 thru E-12 03/21/12
F-3 thru F-4 08/25/10 F-3 thru F-4 03/21/12
J-3 thru J-10 08/25/10 J-3 thru J-12 03/21/12
K-3 thru K-4 06/21/11 K-3 thru K-4 03/21/12
K-11 thru K-14 08/25/10 K-11 thru K-14 03/21/12
L-3 thru L-8 06/21/11 L-3 thru L-8 03/21/12
Insert Pages Dated
11 (and 12)
Change 8260.19E FEDERAL AVIATION ADMINISTRATION U.S. DEPARTMENT OF TRANSPORTATION
CHG 1
CHG 1
Effective Date: National Policy 06/21/2011
SUBJ: Flight Procedures and Airspace
1. Purpose. This order provides guidance to all FAA personnel for the administration and accomplishment of the FAA Flight Procedures and Airspace Program.
2. Audience. The primary audience for this Order is the Air Traffic Organization (ATO), Mission Support Services (MSS), Aeronautical Navigation Products Office (AeroNav Products), who has the responsibility to develop instrument flight procedures. The secondary audience includes the ATO MSS Aeronautical Information Management (AIM) Office (AJV-2), ATO Service Areas' Operational Support Group, Flight Procedures Team (OSG-FPT), Air Traffic’s Technical Operations Aviation System Standards Office (AJV-3); Flight Standards headquarters, and regional office Divisions/Branches.
3. Where You Can Find This Change. You can find this order on the Directives Management System (DMS) Website: http://www.faa.gov/regulations_policies/orders_notices.
4. Effective Date. June 30, 2011
5. Explanation of Changes. Significant areas of new direction, guidance, policy, and criteria as follows:
a. General. Formatting is revised to meet current FAA standards. Paragraphs are realigned for better editorial flow. Office identifications and routing codes are updated to reflect the current FAA organizational structure. All references to other FAA Orders reflect the current edition. All reference to the former AeroNav Services is changed to AeroNav Products. All reference to the former Flight Procedures Office (FPO) is changed to the ATO Service Area Operations Support Group-Flight Procedures Team (OSG-FPT).
b. Table of Contents. Updates Table of Contents to coincide with the pages changed.
c. Chapter 1.
(1) Paragraph 1-6. Provided guidance for the implementation of changes as they relate to the Effective Date.
d. Chapter 2.
Distribution: Electronic Only Initiated By: AFS-420
(1) Paragraph 2-2. Revised to address current processing requests for public procedures.
(2) Paragraph 2-8. Revised environmental impact guidance to show compliance is per applicable environmental directives.
(3) Paragraphs 2-14b and 2-18f(2). Clarification.
(4) Paragraph 2-21a. Specified that FDC NOTAMs are used for all IFP NOTAMs, whether regulatory or not. Prior to this change, NOTAM D was used to promulgate SID and STAR changes.
(5) Paragraph 2-21a(1). Added paragraph to clarify that NTAP publication of FDC NOTAMs relating to instrument approach and departure procedures and ATS routes does not authorize cancellation of the NOTAM.
(6) Paragraph 2-22a(1). Adds that FDC FI/T NOTAMs are used for ATS routes, SIDs, STARs, and Special IFPs.
(7) Paragraph 2-22a(2). Policy added to require a Flight Standards waiver through AFS-460 when it is known that a temporary NOTAM will be required for more than 224-days and a procedure amendment is not desired. Added cross reference for waiver request procedures.
(8) Paragraph 2-22b. Added clarification that P-NOTAMs are promulgated for publication by NFDC through the bi-weekly Transmittal Letter.
(9) Paragraph 2-22b(1). Paragraph expanded to include former subparagraph (5) and more thoroughly explain the use of P-NOTAMs. Remaining subparagraphs re-numbered.
(10) Paragraph 2-22b(3). Paragraph expanded to include SA CAT I/II approaches.
(11) Paragraph 2-22b(6). Adds requirement for coordination a procedure amendment date.
(12) Paragraph 2-23a. New paragraph added to introduce keywords to FDC NOTAMs in support of Air Traffic Organization (ATO) initiatives. Following paragraphs re-numbered.
( 13) Paragraph 2-23b. Added NOTAM responsibility for procedures developed under an Other Transactional Authority (OTA) will be delegated to the service provider.
( 14) Paragraph 2-23c. Consolidated responsibilities of AeroNav Products.
(15) Paragraph 2-23c(3)(a). Eliminated the phrase “or if unable, during the next normal workday.” The 24/7 NOTAM Center should always be able to ensure immediate ARTCC notification. Moved airport manager notification to a separate sub-paragraph.
(16) Paragraph 2-23c(3)(b). New paragraph added to specify procedures to ensure that the airport manager at the affected location is notified whenever possible when an IFP NOTAM is issued.
(17) Paragraph 2-23c(3)(e). Added requirement for the AeroNav Products to notify third-party procedure developers of FAA initiated NOTAMs at locations where OTA procedure development is occurring.
(18) Paragraph 2-23d. Added AFS-460 responsibilities.
(19) Paragraph 2-23e. Added AFS-460 responsibility as the approval authority for waivers to allow temporary NOTAMs extend beyond the 224-day.
(20) Paragraph 2-24. All references to NOTAM Ds for graphic ODPs, SIDs, and STARs have been deleted as these procedures will use the FDC NOTAM process.
(21) Paragraph 2-24d. New paragraph added to mandate FDC NOTAMs for graphic ODPs, SIDs, and STARs.
(22) Paragraph 2-25. New paragraph added to provide guidance for FDC NOTAMs to correct government chart printing or compilation errors. Keyword “CHART” introduced and examples provided. Remaining paragraphs re-numbered.
(23) Paragraph 2-26e. Example RNAV substitution NOTAMs added.
(24) Paragraph 2-26e(2). Requirement added for AFS-400 to advise AeroNav Products when the phrase “OR DME/DME/IRU” may be added to GPS substitution NOTAMs.
(25) Paragraph 2-26h. Added requirement that AeroNav Products must be notified when a CAT II/III suspension will exist longer than 224-days or is permanent so that an appropriate procedure amendment may be made prior to the 224-day suspense.
(26) Paragraph 2-27. Examples updated to demonstrate use of the keyword “ROUTE.”
(27) Paragraph 2-28. Special IFP NOTAM guidance updated.
(28) Paragraph 2-29. Guidance updated to include graphic ODPs, SIDs, and STARs and examples provided.
(29) Paragraph 2-40. Changed to reflect that Flight Standards will direct immediate changes to procedures when criteria are revised.
(30) Paragraph 2-41. DVAs added to periodic review process.
(31) Paragraph 2-63a. Revised responsibilities.
(32) Paragraph 2-64a(10). Added text to exclude RNAV Visual Flight Procedures.
(33) Paragraph 2-64a(11). Removed requirement to establish a CNF when PFAF is less than 1 NM from the FAF.
(34) Paragraph 2-64b. Revised to support current NFDC practices.
(35) Paragraph 2-72. Removed “in all cases” and added exception reference.
(36) Paragraph 2-72b(2), (3), (4), & (6). Editorial.
(37) Paragraph 2-74b(3)(a). Added Note.
(38) Paragraph 2-75c. Revised vertical Datum application for WAAS/LAAS.
e. Chapter 4.
(1) Paragraph 4-5d(2). Revised coordination conflicts responsibilities.
(2) Paragraph 4-5e(1). Removed requirement to apply “Z” suffix to procedure containing lowest minima.
(3) Paragraph 4-5s. Revised to refer to Order 6560.10 for Runway Visual Range (RVR) installation requirement.
(4) Paragraph 4-40 to 4-46. Revised to incorporate Form 8260-7A/B guidance.
(5) Paragraph 4-41c. Revised name to Mission Support Services and broke out responsibilities for Operations Support Group – Flight Procedures Team and AeroNav Products.
(6) Paragraph 4-42a. Revised text addressing OE Study Plan guidance.
(7) Paragraph 4-61b(2). Deleted slash.
(8) Paragraph 4-01e. Corrected paragraph number.
(9) Paragraph 4-94h. Refined definition.
(10) Paragraph 4-97. Deleted Note 2.
(11) Paragraph 4-99j. Editorial change for clarification.
f. Chapter 5.
(1) Paragraph 5-3e. Revised for clarification on application of accuracy code.
(2) Paragraph 5-8g(2)(d). Inserted “penetration turn completion.”
g. Chapter 8.
(1) Paragraph 8-2c. Added reference to Form 8260-7B.
(2) Paragraph 8-6i(4). Added reference to see paragraph 8-52b(3) for limitation on profile view charting.
(3) Paragraph 8-11c(4). Revised to support current NFDC practices.
(4) Paragraph 8-11c(5). Clarified what to do when a deviation to an Effective Date is necessary.
(5) Paragraph 8-11d. Change AFS-420 to AFS-460.
(6) Paragraph 8-11i. Deleted reference to Form 8260-7.
(7) Paragraph 8-12. Added option to suspend a procedure.
(8) Table 8-1. Updated to include Forms 8260-7A and 8260-7B.
(9) Paragraph 8-30e Note 3. Added, recommend RNGP consultation when establishing an equivalent level of safety.
(10) Paragraph 8-40a. Revised responsibilities.
(11) Paragraph 8-41h(1). Deleted; instructions to document Minimum Turning Altitudes (MTA) and moved documentation instructions to paragraph 8-80.
(12) Paragraph 8-41m. Added Note for date to be used when the fix/holding pattern is for a Special.
(13) Paragraph 8-41i(2). Added requirement to change revision number when “Fix Use” is changed (i.e., addition, deletion, or modification.
(14) Paragraph 8-41s. Revised distribution text, removing AeroNav Services.
(15) Paragraph 8-51b. Added guidance for step-down segments.
(16) Paragraph 8-52a(3). Deleted; paragraph 8-52a(4) becomes the new paragraph 8-52a(3).
(17) Paragraph 8-52b(3). Revised to address multiple intermediate segments.
(18) Paragraph 8-52c(2)(a). Note. Added “RNP.”
(19) Paragraph 8-52d Note. Revised guidance regarding application of a step-down fix when LP and LNAV procedures are published on the same chart.
(20) Paragraph 8-52f(1). Removed additional GS/GP intercept altitude requirements for simultaneous operations.
(21) Paragraph 8-54a. Established a minima hierarchy and limited number of lines of minimum.
(22) Paragraph 8-54g(3) & 8-54i(3) Note. Changed “Special Aircraft and Aircrew Authorization Required” to “Authorization Required.”
(23) Paragraph 8-54g(4). Added guidance for GLS minimums.
(24) Paragraph 8-54k. Revised paragraph to support SA CAT I and SA CAT II.
(25) Paragraph 8-54m(6). Deleted “circling’ option.
(26) Paragraph 8-54m(7). Paragraph rewritten to support Simultaneous Independent Parallel Approaches (SIPIA) operations.
(27) Paragraph 8-55a. Added guidance for documentation regarding Notes that apply to only one procedure when multiple procedures are documented on the form.
(28) Paragraph 8-55a(1)/(2). Added VGSI and TCH to chart text.
(29) Paragraph 8-55f. Updated to include newer AWOS types.
(30) Paragraph 8-55m(5). Revised for clarity.
(31) Paragraph 8-55s(5). Revised text for clarity.
(32) Paragraph 8-56a. Added clarification guidance terminal point guidance.
(33) Paragraph 8-56c. Deleted reference to circling.
(34) Paragraph 8-56c(1). Deleted reference to circling.
(35) Paragraph 8-56e. Editorial changes.
(36) Paragraph 8-56e(1). Added guidance to permit use of additional attention symbols and provided examples.
(37) Paragraph 8-56e(2). Added text to permit the development of a second chart to support a standard climb gradient.
(38) Paragraph 8-56e(3). Added that nonstandard climb gradients not be used for circling procedures.
(39) Paragraph 8-57v. Added “(name)” to better define segment beginning.
(40) Paragraph 8-58d(3). Added SA CAT I and SA CAT II options.
(41) Paragraph 8-58e(1)(g). Removed requirement to cancel and establish an original procedure when transferring Special instrument procedure responsibilities.
(42) Paragraph 8-58e(2)(h). Added the ability to add/delete/modify any straight-in procedure suffix by amendment.
(43) Paragraph 8-58e(6). Removed reference to database.
(44) Paragraph 8-60a(1)(a) & (b). Added guidance for RNP application.
(45) Paragraph 8-72. Revised to support new FAA Form 8260-7A & 8260-7B.
(46) Section 10. Revised to support new FAA Form 8260-16 report format.
(47) Paragraph 8-80i & 8-80j. Added guidance for Minimum Turning Altitude (MTA).
h. Appendix A. Changed minimum to medium. Added ATS, IPDS, NTS, No PT, and TPP. Corrected VM. Amended LP. Deleted FPFO.
i. Appendix B. Updated text, Orders, and Advisory Circulars
j. Appendix D. Expanded instructions.
k. Appendix I. Revised forms 8260-7 to establish new forms 8260-7A and 8260-7B.
l. Appendix K. Editorial change to remove (GPS) from samples.
m. Appendix L. Updated to new requirements in RTCA DO-2298.
06/21/2011 8260.19ECHG1
PAGE CONTROL CHART
Insert Pages
i thru xii
1-1 thru 1-12
2-1 thru 2-6
2-9 thru 2-54
4-1 thru 4-44
5-1 thru 5-2
5-27 thru 5-28
8-1 thru 8-118
A-l thruA-6
B-l thru B-4
D-lthruD-2
1-1 thru 1-6
K-3thruK-10
Dated Remove Pages
i thru xii
1-1 thru 1-12
2-1 thru 2-6
2-9 thru 2-54
4-1 thru 4-44
5-1 thru 5-2
5-27 thru 5-28
8-1 thru 8-98
A-l thruA-6
B-l thruB-4
D-lthruD-2
1-1 thru 1-4
K-3thruK-10
John M. Allen
Dated
08/25/10
08/25/10
08/25/10
08/25/10
08/25/10
08/25/10
08/25/10
08/25/10
08/25/10
08/25/10
08/25/10
08/25/10
08/25/10
Director, Flight Standards Service
Basic Order
U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
National Policy
Order
8260.19E
. FAA Logo Effective Date: August 25, 2010
SUBJ: Flight Procedures and Airspace
1. This order provides guidance to all FAA personnel for the administration and accomplishment of the FAA Flight Procedures and Airspace Program.
2. The development of effective and efficient flight procedures is closely related to the facility establishment and airport programs, and requires active participation by Flight Standards and the applicable Air Traffic Organization Service Area personnel in the planning, programming, and budgeting of navigation facilities and airport development plans. Instrument procedures often determine the alignment and location of navigation facilities as well as the location, marking, and lighting of airport landing and maneuvering areas. Minimum en route altitude (MEA), minimum reception altitude (MRA), maximum authorized altitude (MAA), minimum obstruction clearance altitude (MOCA), minimum crossing altitude (MCA), and changeover point (COP) are established by the Federal Aviation Administration for instrument flight along Federal airways in Title 14 Code of Federal Regulations (CFR) Part 95.
3. Guidelines and procedures that are common to all instrument flight procedures are in Chapter 1. Specific guidelines and procedures for en route and terminal instrument flight procedures are contained in chapters 3 and 4, respectively. Chapter 5 contains information concerning Airspace - Obstruction Evaluation (OE); Designation of Controlled Airspace; Airport Airspace Analysis; Restricted Areas; and Establishment, Relocation, or Discontinuance of Radio Navigation Aids. Chapter 6 provides information concerning Military Procedures. Chapter 7 contains - Planning Standards; Airway, Terminal, and Airport Planning; Safety Analysis; Private Aid; and Facilities and Equipment (F&E) Support. Chapter 8 provides information on Instrument Approach Procedures Data Transmittal Systems as well as the use and preparation of forms.
Original Signed By John W. McGraw
John M. Allen Director Flight Standards Service
02/22/13 8260 19ECHG3
Table of Contents
Paragraph Page
Chapter 1.
Section 1.
1-1 1-2 1-3 1 4 1-5 1 -6 1-7-1-9
Section 2.
1-10 1-11 1-12 1-13 1-14 1-15 1-16 1-17-1-19
Section 3.
20 21 22 23 24 25 26 •1-99
Chapter 2.
Section 1.
2-1 2-2 2-3 2-4
Section 2.
2-5 2-6
Administrative
General
Purpose of This Order Audience Where You Can Find This Order What This Order Cancels Explanation of Changes Effective Date Reserved
Responsibilities
Flight Standards Service (AFS-1) 1-2 Flight Technologies and Procedures Division (AFS-400) 1-2 Regional Flight Standards Divisions (AXX-200) 1-4 Technical Operations, Flight Inspection Services (AJW-3) 1-5 Air Traffic Organization, Mission Support Services (AJV-0) 1-6 Individual 1-9 Transferring Instrument Procedure Maintenance Responsibilities 1-9 Reserved 1-10
Instrument Procedure Development Software Responsibilities
Background 1-11 Flight Procedure Standards Branch's Responsibility 1-11 Aeronautical Navigation (AeroNav) Products (AJV-3) Responsibility 1-11 Office of Information Services (AMI-1) 1-12 Office of Assistant Administrator for Information Services (AIO-1) 1-13 Vice President for Mission Support Services (AJV-0) 1-13 Reserved 1-13
General Procedures
General
General 2-1 Requests for Public-Use Instrument Flight Procedures 2-1 Air Traffic Letters of Agreement 2-1 Airport Lighting and Visual Aids 2-1
Aeronautical Charts
Use of Maps and Charts 2-3 Aeronautical Charts and Publications 2-3
02/22/13 8260 19ECHG3
Table of Contents (Continued)
Paragraph
Section 3. Environmental Requirements
2-7 Noise Abatement
2-8 Environmental Impacts
Section 4. Facility Utilization and Monitoring
2-9 Frequency Service Volumes 2-10 ATC Usable Distance and Altitude Limitations 2-11 Requests for Expanded Service Volumes (ESV) 2-12 Utilization of Localizers as En Route Aids 2-13 Monitoring of Navigation Facilities 2-14 Utilization of Monitoring Categories 2-15 Utilization of 75 Mhz Markers Section 5. Implementing Epoch Year Magnetic Variation (MV)
2-16 General 2-17 Responsibilities 2-18 Guidelines 2-19 Reserved
Section 6. Notices to Airmen (NOTAMs)
2-20 General 2-21 United States NOTAM System 2-22 FDC NOTAM Types 2-23 FDC NOTAM Preparation, Review, and Transmittal Responsibilities 2-24 Instrument Flight Procedure NOTAMS 2-25 Chart Correction NOTAMS 2-26 General NOTAM D Actions 2-27 Air Traffic Service (ATS) NOTAMs 2-28 FDC NOTAMs for Special Instrument Approach Procedures (Specials) 2-29 NOTAM Content
Section 7. Quality/Standardization of Instrument Flight Procedures
2-30 AeroNav Products Action 2-31 AFS-460 Action 2-32-2-39 Reserved
Section 8. Periodic Review of Instrument Flight Procedures
2-40 General 2-41 AeroNav Products Action 2-42-2-49 Reserved
Page
2-5 2-5
2-6 2-6 2-9 2-10 2-10 2-11 2-11
2-13 2-13 2-18 2-19
2-20 2-20 2-20 2-22 2-25 2-26 2-27 2-29 2-30 2-31
2-35 2-35 2-35
2-36 2-37 2-38
02/22/13 8260.19ECHG3
Table of Contents (Continued)
Paragraph Page
Section 9. Communications and Weather
2-50 Communications Requirements 2-39 2-51 Use of UNICOM 2-39 2-52 Automatic Altimeter Setting and Weather Reporting Systems 2-40 2-53-2-59 Reserved 2-40
Section 10. Navigational Fixes
2-60 General 2-41 2-61 Reporting Points 2-41 2-62 Unplanned Holding at Designated Reporting Points 2-41 2-63 Requests for Navigational Fixes 2-41 2-64 Naming Navigational Fixes 2-42 2-65 Documenting Navigational Fixes 2-44 2-66 Correlation of Navigational Fixes and Changeover Points (COPs) 2-44 2-67 Minimum Reception Altitudes (MRA) 2-45 2-68 Flight Inspection 2-45 2-69 Maximum Authorized Altitudes (MAA) 2-45
Section 11. Obstacle Data
2-70 General 2-46 2-71 Obstacle Data Sources 2-46 2-72 Obstacle Data Accuracy Standards 2-46 2-73 Accuracy Standards Application 2-48 2-74 Controlling Obstacles 2-49 2-75 Vertical Datums 2-53 2-76-2-79 Reserved 2-54
Section 12. Waiver of Standards/Approval Requests
2-80 General 2-55 2-81 Waiver Processing 2-55 2-82 Waivers for Special Instrument Approach Procedures 2-56 2-83 Safety Management System (SMS) Requirements 2-56 2-84 Periodic Review of Waivers 2-57 2-85 Cancellation of Waivers 2-57 2-86-2-99 Reserved 2-57
Chapter 3. En Route Procedures
SECTION 1. GENERAL
3-1 General 3-1 3-2 Publication 3-1
3-3-3-19 Reserved 3-1
Section 2. Criteria Application and Development
3-20 Criteria Application 3-2 3-21 Development of Criteria 3-2 3-22-3-29 Reserved 3-2
02/22/13 8260.19ECHG3
Table of Contents (Continued)
Paragraph Page
Section 3. Establishment of En Route Airspace
3-30. Relationship of COPs to Airspace Dimensions 3-3 3-31. Relationship of MEAs to Controlled Airspace Floors 3-3
3-32.-3-39. Reserved 3-3
Section 4. Substitute En Route Flight Procedures
3-40. General 3-4 3-41. Format 3-4 3-42. Facilities Used 3-4 3-43. Controlled Airspace 3-4 3-44 Flight Inspection 3-4 3-45. Planning and Coordination 3-5 3-46. Processing 3-8 3-47. Periodic Review 3-8 3-48. Distribution 3-9 3-49. Reserved 3-9 Section 5. Off-Airway Routes
3-50. Establishment 3-10 3-51. Listing 3-10 3-52. Off-Airway Data 3-10 3-53. Processing Data to NFDC 3-10 3-54.-3-59. Reserved 3-10
Section 6. New or Revised National Airspace System Routes 3-60. Definition 3-11 3-61. Coordination Procedures 3-11 3-62. Publication of Procedural Data 3-11 3-63.-3-69. Reserved 3-11
Section 7. Minimum Vectoring Altitude (MVA) and Minimum IFR Altitude (MIA) Charts 3-70. Chart Preparation 3-12 3-71. Areas of Consideration 3-12 3-72. Obstacle Clearance 3-12 3-73. Obstacle Clearance Reduction 3-13 3-74. Chart Review and Approval 3-13 3-75. Emergency Obstruction Video Map (EOVM) 3-14 3-76.-3-79. Reserved 3-14
Chapter 4. Terminal Procedures
Section 1. General
4-1. General 4-1 4-2. Categories of Instrument Approach Procedures 4-1 4-3. Airspace Requirements 4-1
IV
02/22/13 8260 19ECHG3
Table Of Contents (Continued)
Paragraph
4-4 Contractual Use of Private Facilities 4-5 TERPS Application 4-6 Sidestep Maneuvers 4-7 Temporary Displaced Threshold Procedures 4-8-4-19 Reserved
Section 2. Standard Instrument Approach Procedures (SIAP)
4-20 General 4-21 Coordination of Terminal Instrument Procedures 4-22 Radar Instrument Approach Procedures 4-23-4-29 Reserved
Section 3. Reserved
4-30-4-39 Reserved
Section 4. Special Instrument Procedures Processing
4-40-4-49 Reserved
Section 5. Direction Finder (DF) Procedures
4-50 General 4-51 Format 4-52 Application of Criteria 4-53 DF Vectoring Altitudes 4-54 DF Vector Area 4-55 Distribution 4-56 Cancellation of DF Procedures 4-57 -4-59 Reserved
Section 6. Category II and III ILS
4-60 General 4-61 Action 4-62 NOTAM Requirements 4-63-4-69 Reserved
Section 7. Departure Procedures (DP)
4-70 General 4-71 Diverse Vector Area (DVA) 4-72-4-79 Reserved
Page
4-2 4-2 4-7 4-9 4-10
4-11 4-11 4-11 4-11
4-12
4-13
4-14 4-14 4-14 4-15 4-15 4-15 4-15 4-15
4-16 4-17 4-18 4-18
4-19 4-19 4-19
02/22/13 8260 19ECHG3
Table of Contents (Continued)
Paragraph
Section 8. Standard Terminal Arrival (STAR)
4-80 Introduction 4-81 AeroNav Services Action 4-82-4-89 Reserved
Section 9. RNAV Procedure Development
4-90 General 4-91 RNAV Approach Procedure Design 4-92 Developing RNAV Waypoint 4-93 RNAV Leg Types 4-94 RNAV Leg Type Descriptions 4-95 Final Approach Segment (FAS) Data 4-96 Remote Altimeter Setting for Baro-VNAV 4-97 Critical Temperature 4-98 DME/DME Screening Model 4-99 Additional Documentation
Chapter 5. Airspace
Section 1. Obstruction Evaluation (OE)
5-1 General 5-2 Responsibility and Processing of FAA Form 7460-1 5-3 Review of Notices 5-4 Obstructions Under Subpart C, 14 CFR Part 77
Section 2. Designation of Controlled Airspace
5-5 General 5-6 Air Traffic Responsibility 5-7 AeroNav Services Action 5-8 Terminal Airspace
Section 3. Airport Airspace Analysis
5-9 General 5-10 AeroNav Services/AFS Inputs in Establishment of Airports and Heliports 5-11 Alterations of Airports or Heliports 5-12 Deactivation of Airports or Heliports 5-13 Assistance in Zoning Problems
Section 4. Reserved
5-14-5-16 Reserved
Page
4-20 4-20 4-21
4-22 4-22 4-24 4-26 4-27 4-28 4-28 4-28 4-29 4-29
5-1 5-1 5-1 5-4
5-5 5-5 5-5 5-5
5-33 5-33 5-34 5-34 5-35
5-36
VI
02/22/13 8260 19ECHG3
Table of Contents (Continued)
Paragraph Page
Section 5.
5-17 5-18
5-19
Section 6.
5-20 5-21 5-22 5-23 -5-99 Chapter 6.
6-1 6-2 6-3 6-4 6-5 -6-99
Chapter 7.
Section 1.
7-1
Section 2.
7-2 7-3
Section 3.
7-4
Section 4.
7-5
Section 5.
7-6 7-7
Section 6
7-8
Restricted Areas
General Letter of Procedures
Reserved
Establishment, Relocation, or Discontinuance of Radio Navigation Aids
Criteria and Guidelines AeroNav Services Action AFS Action Reserved Military Procedures
General Review and Coordination FAA Acceptance Assistance Reserved
Planning
General
General
Planning Standards
Planning Standards Determination of Operational
Safety Analysis
Performing a Safety Analysis
Airway Planning
General
Terminal Planning
General Requirements for Outer Com
Airport Planning
General
5-37 5-37 5-37
5-38 5-38 5-38 5-38
6-1 6-1 6-1 6-1 6-1
7-1
7-2 7-2
7-4
7-7
7-8 7-8
7-14
VII
02/22/13 8260 19ECHG3
Table of Contents (Continued)
Paragraph Page
Section 7. Private Aid
7-9 General 7-16
Section 8 Facility and Equipment (F&E) Support
7-10 Support 7-17
7-11-7-99 Reserved 7-17
Chapter 8. Instrument Approach Procedures Data Transmittal System
Section 1. General
8-1 General 8-1
Section 2. Form Use and Preparation
8-2 Use of Forms 8-2 8-3 Form Preparation 8-2 8-4 Course and Distance Information 8-3 8-5 Communications Data 8-4 8-6 Terminal Routes General 8-5 8-7 Terminal Fixes 8-8 8-8-8-9 Reserved 8-10 Section 3 Certification, Processing, and Review
8-10 General 8-11 8-11 Certification and Distribution of SIAPs 8-10 8-12 Cancellation/Suspension of Instrument Approach Procedures 8-13 8-13 Revisions to Instrument Flight Procedures (IFPs) 8-14 8-14 Processing 8-19 8-15 AeroNav Products Review of SIAPs and Charts 8-19 8-16 AeroNav Products Action 8-19 8-17-8-19 Reserved 8-19
Section 4. Reserved
8-20 -8-29 Reserved 8-23
Section 5 Flight Procedures Standards Waiver, FAA Form 8260-1
8-30 8-24 Preparation of FAA Form 8260-1, Flight Procedures Standards Waiver
8-26 8-31 -8-39 Reserved
Section 6. Radio Fix and Holding Data Record, FAA Form 8260-2
8-40 Introduction 8-29 8-41 Preparation of FAA Form 8260-2 8-30 8-42 -8-49 Reserved 8-39
VIII
8-43
02/22/13 8260.19ECHG3
Table of Contents (Continued)
Paragraph Page
Section 7. Completion of FAA Forms 8260-3/5
8-50. General 8-40 8-51. Terminal Routes 8-40 8-52. Lines 1 through 8 8-53. Takeoff and Alternate Minimums 8-50 8-54. Minimums 8-51 8-55. Notes 8-52 8-56. Missed Approach 8-71 8-57. Additional Flight Data 8-76 8-58. Lower Blocks 8-82 8-59. Reserved 8-85
Section 8. Standard Instrument Approach Procedure Data Record, FAA Form 8260-9
8-60. Preparation of FAA Form 8260-9 8-86
8-61.-8-69. Reserved 8-94
Section 9. Completion of Forms 8260-4/7/10
8-70. General 8-95 8-71. Form 8260-4, Radar 8-95 8-72. Form 8260-7, Special Instrument Approach Procedure 8-96 8-73. Form 8260-10, Continuation Sheet 8-99 8-74.-8-79. Reserved 8-99 Section 10. Transmittal of airways - Route Data, FAA Form 8260-16
8-80. Preparation of FAA Form 8260-16 8-100
8-81.-8-89. Reserved 8-104
Appendix A. Administrative Information (6 Pages)
1. Distribution A-1 2. Terms, Definitions, and Acronyms A-1 3. Forms A-5 4. Information Update A-6 Appendix B. Flight Procedures References (4 Pages)
Orders and Notice B-1 Advisory Circulars B-3 Title 14, Code of Federal Regulations (CFR) B-4 Other Publications B-4
Appendix C. Obstacle Accuracy Standards, Codes, and Sources (6 Pages)
1. United States National Map Accuracy Standard C-1 2. Accuracy Codes and Sources C-2
IX
02/22/13 8260 1 9 E C H G 3
Table of Contents (Continued)
Paragraph Page
Appendix D. Data Worksheet for FAA Form 8260-2, Radio Fix and Holding Data Record
Data Worksheet Instructions D-1
Sample DATA Worksheet for FAA Form 1320-2, D-2
Appendix E. Radio Fix and Holding Data Record, FAA Form 8260-2
Sample FAA Forms 8260-2 (Front and Back) Appendix F. ILS and RNAV Standard Instrument Approach Procedure, FAA Form 8260-3
E-3 thru E-12
Sample FAA Forms 8260 3 (Front and Back) F-3 thru F-4
Appendix G. Radar - Standard Instrument Approach Procedure, FAA Form 8260-4
Sample FAA Form 8260-4 (Front and Back) G-3 thru G-4
Appendix H. Standard Instrument Approach Procedure, FAA Form 8260-5
Sample FAA Forms 8260-5 (Front and Back Sides) H-3 thru H-4
Appendix I. Special Instrument Approach Procedure, FAA Form 8260-7 and Special Instrument Approach Procedure Authorization, FAA Form 8260-7B
Sample FAA Form 8260-7A (Front and Back Sides) Sample FAA Form 8260-7B (Front and Back Sides)
I-3 thru I-4 I-5 thru I-6
Appendix J. Standard Instrument Approach Procedure Data Record, FAA Form 8260-9
Sample FAA Forms 8260-9 (Front and Back Sides) J-3 thru J-60
Appendix K. Standard Instrument Approach Procedure Continuation Sheet, FAA Form 8260-10
Sample FAA Form 8260-10 (Front and Back Sides) K-3 thru K-14
Appendix L. Final Approach Segment (FAS) Data Block Cyclic Redundancy Check (CRC) Requirements
Contents of the FAS Data Block 1 Fields needed for the Final Approach Segment (FAS) Data Block 2 Fields needed for Integrity Monitoring 3 Fields not Included in the FAS Data Block 4 Explanation of Data Field Entries
L-1 L-1 L-2 L-2
Table of Contents (Continued)
Paragraph Page
Appendix M. Final Approach Segment (FAS) Data Block Cyclic Redundancy Check (CRC) Requirements for Helicopter Operations
Contents of the FAS Data Block 1. Fields needed for the Final Approach Segment (FAS) Data Block … M-3 2. Fields needed for Integrity Monitoring … M-3 3. Fields not Included in the FAS Data Block … M-4 4. Explanation of Data Field Entries … M-4
Appendix N. ARINC 424 Database Codes
1. Waypoint Description Codes … N-1 2. Waypoint Description Code Definition/Description … N-1
xi (and xii)
Chapter 1. General Information
Section 1. General
1-1. Purpose of This Order. This order provides guidance to all FAA personnel for the administration and accomplishment of the FAA Flight Procedures and Airspace Program.
1-2. Audience. The primary audience for this Order is the Air Traffic Organization (ATO), Mission Support Services (MSS), AeroNav Products (AJV-3), who has the responsibility to develop instrument flight procedures. The secondary audience includes the ATO MSS Aeronautical Information Management Group (AJV-2); the ATO Service Areas' Operational Support Group, Flight Procedures Team (OSG-FPT), the Technical Operations Flight Inspection Services (AJW-3); Flight Standards (AFS) headquarters and regional office Divisions/Branches.
1-3. Where You Can Find This Order. You can find this order on the FAA’s web site at: https://employees.faa.gov/tools_resources/orders_notices/.
1-4. What This Order Cancels. Order 8260.19D, Flight Procedures and Airspace, dated August 7, 2007, is canceled.
1-5. No Substantive Changes to this Order. This order has been totally reformatted in accordance with Order 1320.1E, Directives Management System, and only editorial changes have been made.
1-6. Effective Date. This Order and subsequent changes are effective on the dates shown in the upper left corner of each page. Implementation of changes must commence no later than 24 months from the published effective date. Previous editions may be used until implementation has commenced, not to exceed 24 months from the new effective date.
1-7.-1-9. Reserved.
Section 2. Responsibilities
Note: Organizational responsibilities and functions are addressed in applicable FAA 1100-series Orders. Responsibilities specified in this section are provided for information only and for the purpose of assisting instrument procedure developers in knowing whom to contact for assistance and/or information in the performance of their duties. This section must not be interpreted as a substitute or supplement to any other FAA directive.
1-10. 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.
1-11. Flight Technologies and Procedures Division (AFS-400).
a. This division is the principal element of the Flight Standards Service governing policies, criteria, and standards for establishing and maintaining terminal and en route flight procedures; for using air navigation facilities, appliances, and systems; and for validation of FAA instrument procedure design software. This office is designated as the final authority to issue, amend, and appeal minimum en route instrument flight rules (IFR) altitudes and associated flight data under Title 14, Code of Federal Regulations (14 CFR) Part 95 and standard instrument approach procedures under 14 CFR Part 97. The division is also responsible for approval/ disapproval of special instrument approach procedures and requests for waivers of standards.
b. The Flight Operations Branch (AFS-410), is the principal element of the division with respect to concepts, policies, systems, and programs associated with the operational and flight technical aspects of all weather operations. It develops concepts for design, evaluation, and approval of Category (CAT) I, II, and III approach and landing operations, as well as lower than standard takeoff minimums. Develops instrument flight operational concepts, policies, standards, criteria, requirements, specifications, and limitations for new and existing aircraft (all categories) and new and existing airborne, ground-based and space-based systems used in instrument flight operations, and develops and issues FAA Form 8260-7B, Special Instrument Approach Procedure Authorization, as required, through the Procedures Review Board (PRB). Provides technical representation to International Civil Aviation Organization (ICAO) on matters related to instrument flight operations, and maintains liaison with foreign civil aviation operational and
technical authorities to encourage the acceptance of United States instrument flight operations standards and to foster standards with a level of safety consonant with those of the United States.
c. The Flight Procedure Standards Branch (AFS-420), is the principal element within the division, with respect to the rulemaking process of the flight procedures program; also with respect to the development, application, and oversight of national policies and directives for the administration of the national flight procedures program; and development of criteria pertinent to the design of instrument flight procedures. This branch serves as the focal point within Flight Standards for all matters relating to airspace, cartographic programs, IFP Notices to Airmen (NOTAMs), and is the primary interface for industry on matters relating to instrument procedures criteria. The branch assists the Flight Procedure Implementation and Oversight Branch (AFS-460), providing technical advice and assistance to other FAA elements, government agencies, and industry on the interpretation and application of criteria. It analyzes and evaluates execution of flight procedure programs within the FAA to determine compliance with National policy.
d. The Flight Operations Simulation Branch (AFS-440), is the principal element within the division, 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 air traffic control (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 (IFPs) and Flight Inspection policy oversight. This branch develops policy and provides oversight of the IFP development process for government and non-government service providers. This oversight includes clarifying procedure criteria, confirming procedure development data, conducting simulator evaluations, and monitoring validation flights. AFS-460 develops policy for flight validation of IFPs and manages the program for the review and approval of all Special IFP and Waivers to design criteria and standards. AFS-460, is responsible for coordinating nongovernment procedure developer NOTAM authority and access to the NOTAM Entry System (NES) with ATO Mission Support Services, Aeronautical Information Management (AIM) Office. This branch develops standards to ensure the orderly processing of all approved IFPs and
evaluates the implementation of these standards and practices to determine compliance with established policy. In addition to flight procedure oversight, AFS-460 works with other government agencies, the military, aviation industry leaders, and the international community to improve aviation safety by assisting in the IFP development process worldwide.
g. The Performance Based Navigation Branch (AFS-470), is the principal element within the division, with respect to performance based navigation across all domains. Develops performance based navigation concepts, policies, standards, criteria, requirements, specifications, and limitations for new aircraft and new and existing airborne, ground-based and space-based systems used in instrument flight operations. Develops and issues FAA Form 8260-7B, as required. In coordination with original equipment manufacturers, AIR, and AEGs, identifies and enunciates explicit operating procedures for pilots using new-technology products. Provides guidance to develop Operations Specification (OpsSpec) requirements (including Parts C and H) related performance based navigation, operating minimums, equipment, and training. Responsible for developing concepts, programs, and system requirements necessary to implement performance based navigation and procedures necessary to implement futuristic communications and surveillance capabilities for oceanic, remote area, domestic en route, and terminal area operations, and for nonprecision and precision instrument approaches.
1-12. 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. The RFSDs’ NextGen Branches (RNGB) are assigned specific task processes and derive their guidance for determining appropriate signature level and task responsibilities as specified by their Job Task Analysis.
b. The RNGB responsibilities include but are not limited to the following:
(1) Establishing regional requirements for and managing distribution of, special instrument approach procedures. Receiving and resolving user/industry comments on new and revised special instrument approach procedures. Supporting national programs under the direction of AFS-400 such as the Required Navigation Performance/Authorization Required (RNP/AR) instrument approach procedure (IAP) program.
(2) Providing technical evaluations in support of regional airspace programs to determine the effect on operational safety and visual flight operations. Specific study responsibilities for RFSDs are specified in Order 7400.2, Procedures for Handling Airspace Matters, and dictate involvement in a broad range of technical evaluations (i.e., determining feasibility for CAT II/III operations utilizing RNGB missed approach tool, assessing operational safety for taxiway/runway separation, and configuration relative to a proposed CAT II/III, etc.).
(3) Coordinating the RNGB portion of assigned foreign instrument approach procedures programs as specified in Order 8260.31, Foreign Terminal Instrument Procedures (FTIPs).
(4) Approving for the RFSD each CAT II and III operation and coordinating continuity of service assurance with the ATO Service Area. Related to CAT III approvals is the RFSD focal point for coordinating inter-service Surface Movement Guidance Control System (SMGCS) activities, site inspections, and the approval of the associated SMGCS plan and periodic reviews.
(5) Providing the operational input on matters related to regional capacity studies and airport operational safety initiatives.
(6) Performing Obstruction Evaluation and Airport/Airspace Analysis (OE/AAA) evaluations to address the effect of obstacles on visual flight operations and instrument flight operations (e.g., OE studies) relative to AAA studies, assess operational safety and safety of persons and property on the ground in coordination with the Airports Division, as necessary.
(7) Providing the consolidated RFSD position for review of charted visual flight procedures and area navigation (RNAV) visual flight procedures.
(8) Coordinating with Airports Division in the approval or denial of modifications airport standards, providing written safety assessment of end-around taxiway (EAT) proposals/use and declared distance concepts (see Order 7400.2, Procedures for Handling Airspace Matters).
(9) Providing operational review and comments for Air Traffic Technical Operations Service Area’s submission of a NAS Change Proposal (NCP), evaluation of new ATC Towers and similar ATO projects. This activity includes participation in the associated Safety Risk Management Document (SRMD) analysis and acceptance processes.
(10) When requested by the Flight Procedures Field Office (FPFO), assists in developing the equivalent level of safety for an AeroNav Products originated procedures waiver.
(11) In coordination with AFS-460, participates in and provides region level support when requested for activities related to Third Party Procedure Providers.
1-13. Technical Operations Flight Inspection Services (AJW-3).
a. AJW-3 is the principal element within the Technical Operations Services (AJW-0) directly responsible for the in-flight inspection of air navigation facilities 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. 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. Flight Program Services Group (FPSG) is the AJW-3 element responsible for flight inspection of navigation aids and flight procedures in support of the NAS. The group initiates and completes investigative remedial action with respect to any deficiency or reported hazard,
including restrictions or emergency revisions to procedures. It maintains liaison with AeroNav Products, as well as other FAA offices, civil and military interests, to ensure consideration of all requirements relating to the procedural use of navigation facilities. It maintains a suitable record system reflecting the status of each flight procedure with required supporting data.
1-14. Air Traffic Organization, Mission Support Services (AJV-0).
a. Aeronautical Information Management Office (AJV-2) is directly responsible for managing the agency’s program to provide aeronautical information services to ensure the flow of information necessary for safety, regularity, and efficiency of air navigation. This office is charged with the responsibility for collecting, collating, validating, maintaining, and disseminating aeronautical data regarding the United States and its territories. It is also a source for technical assistance to the Aeronautical Navigation Products Office (AeroNav Products), AJV-3 regarding database accuracy standards, content, and format.
(1) The National Flight Data Center, (NFDC), is the principal element within AJV-2 with respect to maintaining the National Airspace System Resources (NASR) database and for disseminating information relating to the NAS. NFDC is also responsible for maintaining proposed data for the development of instrument flight procedures. NFDC responsibilities include but are not limited to:
(a) Publishing the daily National Flight Data Digest (NFDD) and 56-day subscriber files to promulgate additions, changes, and deletions to non-regulatory elements of the NAS. Respective changes are also published in Order JO 7340.2, Contractions, and Order JO 7350.8, Location Identifiers.
(b) Conducting pre-publication review of aeronautical data contained in standard instrument approach and departure procedures, standard terminal arrivals, standard instrument departures, military training routes, navigational aids, airport data, and airspace changes submitted for action, and to identify and correct items in non-conformance with applicable directives.
(c) Validating submitted data with the NASR Database and resolving contradictions.
(d) Managing the development and assignment of five-letter fix names and navigational aid (NAVAID)/airport identifiers.
(e) Promulgating SIAPs, obstacle departure procedures (ODPs), and permanent FDC NOTAMs relating to IFPs with assigned effective dates in a bi-weekly transmittal letter and completing necessary requirements for publication in 14 CFR Part 97.
(f) Issuing, on a predetermined schedule, amendments to 14 CFR Part 95.
(g) Maintaining copies of FAA 8260- and 7100-series forms that support public use SIAPs, fixes, airways, STARs, and DPs.
(2) The Geographic Services Group is the principal element within AJV-2 responsible for developing, directing, and recommending national policy and criteria for aeronautical information. This group serves as the Mission Support Services focal point for developing and managing Geographic Information Systems for the NAS. Geographic Services is also responsible for collecting, validating, and maintaining obstacle data to support instrument flight procedure development including minimum vectoring altitude (MVA) and minimum IFR altitude (MIA) charts as well as minimum safe altitude warning (MSAW) data creation. Responsibilities include but are not limited to:
(a) Establishing the U.S. position for AIM and Aeronautical Information Services through the International Civil Aviation Organization (ICAO).
(b) Collecting, validating, managing and disseminating as-built obstacle data reported under 14 CFR Part 77.
1. Providing the publically-available Digital Obstacle File (DOF), which contains a record of all as-built man-made obstructions that effect domestic aeronautical charting products.
2. Providing Obstacle Repository System (ORS) data to other FAA offices on a timely basis.
(c) Verifying source data for as-built obstacles and assigning accuracy codes that reflect the reliability of the reported obstacle's vertical height and horizontal position.
(d) Managing the verification/validation of airport survey safety critical data.
(e) Managing the requirements and technology for Telephony, NASR, AIRNAV, Airport GIS, TPSS, AMDB, and the Airspace Design and Analysis Center (SDAT, TFR, SAA, Controlled) databases and infrastructure.
b. Aeronautical Navigation Products (AeroNav Products) (AJV-3) is the FAA element responsible for the development, maintenance, quality assurance, and technical approval of publicuse flight procedures, production and distribution of aeronautical charts and related publications and products. Responsibilities include but are not limited to the following:
(1) Development, publication and maintenance of Standard Instrument Approach Procedures (SIAPs).
(2) Development, publication and maintenance of Obstacle Departure Procedures (ODPs) and Standard Instrument Departure Procedures (SIDs). Development and maintenance of Diverse Vector Areas (DVAs).
(3) Development, publication and maintenance of Air Traffic Service (ATS) Routes.
(4) Review and publication of Standard Terminal Arrivals (STAR) Airport Diagrams, and Special Graphics.
(5) Responsible for quality assurance of items produced by AeroNav Products.
(6) Operations support, as requested, for NAS related products.
(7) Selecting and evaluating source data for final chart compilation.
(8) Validating geographical positions, distances, and bearings of items produced by AeroNav Products.
(9) Maintaining liaison with elements of FAA to support safe and accurate portrayal of charting data.
(10) Providing civilian charts in support of military requirements.
(11) Providing international charting support to selected foreign countries.
(12) Establishes procedures to ensure operational data are included in the National Airspace System Resources (NASR) database.
(13) Analyzing obstruction evaluations to determine the effects on current and planned instrument flight operations, minimums, and/or flight altitudes of all civil, joint-use, and United States Army instrument procedures in accordance with current policy.
c. Service Area, Operational Support Group, Flight Procedures Teams (OSG-FPTs), responsibilities include but are not limited to:
(1) Evaluating and responding to industry and user comments relating to instrument procedures.
(2) Serving as Chairperson of the Regional Airspace and Procedures Team (RAPT) under Order 8260.43.
(3) Coordinating requests for new instrument procedures service with the respective Air Traffic Service Area and other concerned offices, and conducting instrument procedures feasibility studies.
(4) Coordinating submission by responsible offices of all pertinent data and supporting documents required for procedures development and assignment of priority when further procedures action is required.
(5) Planning and coordinating new or relocated NAS facilities.
(6) Coordinating with applicable Air Traffic Service Areas to select a charting date consistent with priorities and workload when a component of the NAS is to be commissioned, de-commissioned, or altered.
(7) Coordinating the input for the planning and development of Regional and Air Traffic Service Area F&E budget submissions and programming actions.
(8) Evaluating regional airport and airspace changes for impact on instrument flight procedures.
(9) Determining the necessity for environmental impact studies as required by current policy.
(10) Acting as the focal point for flight inspection issues within the region.
1-15. Individual. Personnel working within the Flight Procedures Program are responsible for maintaining professional knowledge in a technical, complex, and specialized field, and for the application of the knowledge to assure safety and practicality in air navigation. Where directives are deficient, each individual must take the initiative to seek an acceptable method of resolution and to inform the responsible office of any recommended change to policy, procedures, etc. that is cost beneficial and/or provides increased operational safety.
1-16. Transferring Instrument Procedure Maintenance Responsibilities. Instrument procedures are normally maintained by AeroNav Products; however, special procedures may be maintained by the proponent. The proponent must show that they are capable of meeting all the requirements stipulated in Order 8260.60. Procedures currently maintained by the FAA may be released to the proponent for maintenance after the following requirements have been met:
a. Proponent submits a written request to AFS-400 to seek approval to assume maintenance responsibilities from AeroNav Products. This request must indicate how the requirements specified in Order 8260.60 will be met.
b. AFS-400 responds to the proponent with approval or disapproval. If the transfer is approved, the proponent will contact AeroNav Products to address the following:
(1) Establish transfer date.
(2) Inform the Regional Airspace Procedures Team (RAPT) that the maintenance responsibilities for (specified) instrument procedures have been transferred to the proponent.
Note: Include the (maintenance) point-of-contact to ensure all potential correspondence (e.g., OE studies, etc.) from members of the RAPT reaches the proper parties.
(3) Renegotiate reimbursable agreement regarding all required continuing services (e.g., Flight Inspection, etc.).
(4) Coordinate transfer of documentation files to include all applicable FAA 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.
1-17.-1-19. Reserved.
Section 3. Instrument Procedure Development
Software Responsibilities
1-20. Background.
a. The FAA has developed software to implement the Instrument Flight Procedures Program to include the development, review, storage, and electronic transmittal of instrument flight procedures with ancillary system benefits.
b. The FAA instrument procedure software applies criteria specified in Order 8260.3, United States Standard for Terminal Instrument Procedures (TERPS); Order 8260.19, Flight Procedures and Airspace; and other appropriate directives, advisory circulars, software specifications, and CFRs.
1-21. Flight Procedure Standards Branch’s Responsibility. AFS-420 is the office of primary interest and is responsible for software requirements related to administration of the National Flight Procedures Program and for implementation of criteria pertinent to the design of instrument flight procedures.
1-22. Aeronautical Navigation (AeroNav) Products (AJV-3) Responsibility. This is the office of primary interest that is responsible for overall functional management of the FAA instrument procedures software and for ensuring the implementation of AFS-420 defined software requirements.
a. AeroNav Products is responsible for administrative control of instrument procedure software, as well as coordinating actions required to meet changing legal and user requirements. In addition, this group is responsible for:
(1) Carrying out the development of instrument procedure software by coordinating the efforts of users, developers, operators, and contractors associated with instrument procedure software.
(2) Managing and reporting on project schedules, costs, and other supporting resources for the Air Traffic Technical Operations Service Information Resource Manager.
(3) Establishing and maintaining a positive change control management system through the developmental and implementation phases to assure that the completed project (the operational instrument procedure software) meets the requirements of the system definition.
(4) Determining that all proposed changes are essential to the development task and are coordinated among all prospective users of the system.
(5) Keeping contracting officers advised, if appropriate, on proposed changes in order that the officer may be alerted to the impact that they may have on current or proposed contractual actions.
(6) Preparing for and participating in validation tests and evaluations of the information system.
(7) Assuring system software is in conformance with established software requirements.
b. Production Technology and ATC Products Group (AJV-36) is responsible for assuring the successful ongoing operation of the data system. In the performance of these responsibilities, the team must:
(1) Establish and maintain a positive change control management system to assure that all changes to the operational instrument procedure software system are cost effective and are coordinated among all parties who use the FAA instrument procedure software.
(2) Develop necessary guidelines for the control and dissemination of data from the FAA instrument procedure software and other assigned systems.
(3) Authorize release of data in special cases where guidelines are not available.
(4) Provide for coordination in data systems where several program elements share primary operational interest.
(5) Establish priorities for task assignments, scheduling, and utilization of personnel and physical resources.
(6) Assure system configuration, documentation, and reliability.
(7) Conduct extensive operational testing and debugging, to assure system software is in conformance with Order 8260.3 and other appropriate directives, advisory circulars, and 14 CFR provisions. Conduct final system certification of software before release to users through coordination with AFS-420.
(8) Review national user requirements and approve system modifications.
(9) Ensure that the provisions of Order 1370.82, Information Systems Security Program, are complied within the security control of computer programs and associated documentation.
c. Aeronautical Information Management Office (AJV-2) is responsible for establishing and maintaining the AIRNAV database in support of instrument procedure software requirements.
1-23. Office of Information Services (AMI-1). The Office of Information Services, AMI-1, is responsible for the software development from its inception through implementation. This office is also responsible for maintenance of system software, and must provide and control automatic data processing (ADP) resources that include:
a. The utilization of personnel (including contract personnel) and physical resources.
b. Providing technical consultation and advice as required.
c. Providing telecommunications support, and other necessary ADP enhancement and support services for instrument procedure software.
d. Participating in the review of site preparation, installation, and testing support as required.
e. Providing on-site hardware and software installation and testing support as required.
f. Providing preliminary testing of software to assure conformance with established software requirements.
1-24. Office of Assistant Administrator for Information Services (AIO-1). The Office of Assistant Administrator for Information Services, AIO-1, will develop governing policies and responsibilities for automatic data processing (ADP) program management in accordance with Order 1370.52, Information Resources Policy.
1-25. Vice President for Mission Support Services (AJV-0). The Vice President for Mission Support Services is responsible for the determination of agency-wide priorities for use and control of telecommunications resources needed to support FAA instrument procedure software. This responsibility is administered through the Telecommunications Integrated Product Team in the NAS Operations Program (AOP) of the Air Traffic Organization, Technical Operations.
1-26.-1-99. Reserved.
1-13 (and 1-14)
Chapter 2. GeneralProcedures
Section 1. General
2-1. This chapter provides guidelines and procedures that are common to all instrument flight procedures. Specific guidelines and procedures for en route and terminal instrument flight procedures are contained in chapters 3 and 4, respectively.
2-2. Requests for Public-Use Instrument 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 Flight Standards Service (AFS) personnel. See Order 8260.3, United States Standard for Terminal Instrument Procedures (TERPS), Volume 1, chapter 1, paragraph 121.
b. All requests for public-use instrument flight procedures received by any FAA office must be forwarded to the applicable Air Traffic Service Area, Flight Procedures Team (FPT) 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 AeroNav Products. All other projects will be processed as workload permits, by AeroNav Products in order of receipt.
2-3. Air Traffic Letters of Agreement. When letters of agreement affect or include flight procedures, they must be coordinated between ATC facilities and AeroNav Products.
a. When these letters are received, AeroNav Products must review them to ensure compatibility with published or planned flight procedures.
b. Copies of letters of agreement received in AeroNav Products must be made a part of the procedure files, to serve as a reference when developing or amending flight procedures.
c. When the terms of the letters of agreement and flight procedures are not compatible, or if it is determined that the terms do not comply with criteria, AeroNav Products must return the letters to the ATC facility with a memorandum that explains the findings. When appropriate and practical, consideration should be given to adjusting the procedures to accommodate the terms of the agreement.
d. Normally, a letter of agreement is an agreement between two or more ATC facilities. Unless AeroNav Products is a party to the agreement, it is not a signatory and does not approve or disapprove the agreement.
2-4. Airport Lighting and Visual Aids.
a. Operation of airport lighting and visual aids is contained in the following orders:
(1) JO 7110.10, Flight Services.
(2) JO 7110.65, Air Traffic Control.
(3) JO 7210.3, Facility Operation and Administration.
b. Installation criteria are contained in Order 6850.2, Visual Guidance Lighting Systems.
c. Refer to appendix B, Flight Procedures References, for other applicable orders and advisory circulars.
Section 2. Aeronautical Charts
2-5. Use of Maps and Charts.
a. AeroNav Products should maintain an adequate supply of current charts, or electronic equivalent, to support the development of instrument procedures within its area of responsibility. For manual application, the largest scale charts available should be used to develop final, circling, and the first part of the missed approach segment. For precision approach procedures, the Airport Obstruction Chart (OC) or an equivalent plan and profile chart is recommended for use. For all approach procedures, the 7 1/2 and 15-minute quadrangle topographic charts (Quads) produced by the United States Geological Survey provide an excellent source for determining terrain elevation. For efficiency in procedure design and flight inspection, 1:100,000 scale planimetric/topographical (topo) charts are also authorized. Use other data sources such as Digital Obstruction File (DOF), AIRNAV database, AeroNav Products Weekly Obstacle Memo, Digital Terrain Elevation Data (DTED), Digital Elevation Model (DEM), etc., in addition to 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].
2-6. 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 National Airspace (NAS), is the Aeronautical Information Manual (AIM). The primary publication serving as a pre-flight and planning guide for use by United States nonscheduled operators, business, and private aviators flying outside of the United States is the Aeronautical Information Publication (AIP). AFS-400 personnel should conduct periodic surveillance of the AIM and AIP to verify the accuracy and appropriateness of the information. AIM and AIP discrepancies and errors should be forwarded to the Production Technology & ATC Products Group (AJV-36).
c. AeroNav Products personnel should monitor charts or publications released by the FAA that provide informative material, recommended or mandatory, to determine that safe operating practices and conditions are accurately described for aviation users.
d. AeroNav Products is responsible for the accuracy and completeness of flight data submitted by that office for publication. Procedure specialists should review the resulting
published United States Government charts to ensure correct portrayal. AeroNav Products serves as the focal point for questions regarding the procedural data published on these charts.
e. AeroNav Products is responsible for ensuring that United States Government Aeronautical Charts conform to Interagency Air Cartographic Committee (IACC) specifications.
f. The National Flight Data Center (NFDC) serves as the focal point for questions regarding other non-procedural data; e.g., airport/runway data, frequencies, etc. NFDC will resolve questions through the appropriate data source steward.
g. Any FAA personnel who find or are notified of discrepancies and/or errors in aeronautical charts should forward the information to AFS-460, or AeroNav Products, Resource Planning and Management Support (AJV-3A). AIM and AIP discrepancies should be referred to the Production Technology & ATC Products Group (AJV-36).
Section 3. Environmental Requirements
2-7. 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 OSG-FPT. The RFSD must review noise abatement procedures for aircraft performance characteristics and operational safety considerations. The OSG-FPT must review these procedures for practicality and adherence with applicable criteria, and has the primary responsibility for resolving conflicts between IFR procedures and existing or proposed noise abatement procedures.
2-8. Environmental Impacts. Compliance with the following directives: Order 1050.1E, Policies and Procedures for Considering Environmental Impacts, and Order JO 7400.2, Procedures for Handling Airspace Matters, chapter 32, Environmental Matters, is required to meet the environmental compliance requirements of the Agency under the National Environmental Policy Act (NEPA).
Section 4. Facility Utilization and Monitoring
2-9. Frequency Service Volumes. In establishing instrument flight procedures, consideration must be given to the type of navigation facilities available and to their limitations.
a. All electronic navigation facilities are installed in accordance with frequency separation specified in distances and altitudes. Specific frequency protected service volumes are contained in Order 6050.32, Spectrum Management Regulations and Procedures Manual. The Regional Frequency Management Officer (RFMO) primarily uses this order. Order 6050.32 also contains information to facilitate understanding and coordination of operational considerations associated with expanded service volumes.
b. Operational service volume includes the standard service volume (SSV) and expanded service volumes (ESVs). The operational service volume must not extend outside the frequency protected service volume on any radial, at any distance, or at any altitude.
2-10. 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 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. DME/VOR/VORTAC/TACAN.
Facility Usable Height Usable Class Above Facility Distance
(Miles) T 12,000 and below 25 L 18,000 and below 40 H 60,000-45,000 100 Below 45,000-18,000 130 Below 18,000-14,500 100 Below 14,500 40
Note: All elevations shown are with respect to the station’s site elevation.
FigureFigure
F i gure
Figure 2-1. Standard High Altitude Service Volume
Figure 2-2. Standard Low Altitude Service Volume
Figure 2-3. Standard Terminal Service Volume
F i
gu
re
b. Nondirectional Beacon (NDB).
Facility Height Above Distance Class Facility (Miles)
COMLO Note: Low frequency 15 MH beacons have no 25 H standard height 50 HH limitations 75
Note: The COMLO is an NDB of low power, strategically located on an instrument landing system (ILS) approach path to provide L/MF azimuth guidance to an airport, in addition to the more precise guidance of the ILS LOC. COMLOs are normally collocated with ILS Outer Markers (OM) and Middle Markers (MM), and referred to as “LOM” and “LMM,” respectively.
c. Instrument Landing System (ILS).
Facility Height Above Facility Distance (Nautical Miles) Localizer (FC) 4,500 and below 18 Localizer (BC) 4,500 and below 18 Glide Slope (2°-4°) varies with angle 10
d. Microwave Landing System (MLS) [see figures 2-4 and 2-5].
Facility Height Above Distance Facility (Nautical 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
F ig ur
e
Figure 2-5. MLS Elevation Coverage
2-11. Requests for Expanded Service Volumes (ESV).
a. When ATC requires use of navigational aids (NAVAIDs) above/beyond limitations cited in paragraphs 2-11a through 2-11d, ATC submits an ESV request, with a description of the flight procedure requiring it. The Frequency Management Officer (FMO) first reviews this request. The FMO applies the criteria contained in Order 6050.32. If the FMO disapproves the request, it is returned to the originator without further action. FMO approved or restricted ESVs are then reviewed by AeroNav Products.
b. AeroNav Products is responsible for accuracy, clarity, and practicality of the data. If the ESV request is unclear, or if the FMO approved request has restrictions or restrictive comments, it may be necessary to coordinate changes with the FMO and/or the originating office. FAA flight inspection determines if the facility supports the procedure. The flight inspector may utilize facility files and approve the ESV based on supporting data, providing the data was taken within the last five years. If sufficient data are not available, accomplish a flight check of the procedure before AeroNav Products approval.
c. The procedures specialist when developing an instrument procedure may determine a requirement for an ESV; e.g., the instrument procedure is proposed beyond SSV. In this case, the procedures specialist processes an ESV electronically via the Expanded Service Volume Management System (ESVMS website) to obtain the FMO and, in turn, flight inspection approval. An ESV request MUST not be used as a substitute for proper instrument procedure design.
d. Facility rotation due to magnetic variation change should have no effect on coverage; however, radials used will change. AeroNav Products initiates a change action via the Spectrum Management web site (ESVMS) on the date the rotation is effective. Prior to the publication cutoff date AeroNav Products will provide flight inspection a list of the currently approved ESVs against the effected facilities with the new radials and publication date annotated for review/action as appropriate.
e. Describe holding patterns by radial, distance, altitude, and the maximum length holding pattern leg.
f. An ESV is prepared and processed electronically via the ESVMS via the FAA Intranet web site. An ESV can be placed on any very high frequency omnidirectional range (VOR), instrument landing system–distant measuring equipment (ILS-DME), or tactical air navigation (TACAN). When a DME or TACAN and VOR are paired, both must have identical ESVs for safety reasons [except in those cases where the DME ESV supports DME/DME area navigation (RNAV) operations]. ESVs may be added to any class of NAVAID facilities, including NDBs.
2-12. Utilization of Localizers as En Route Aids. The use of a localizer in en route flight procedures may be authorized in accordance with the following limitations:
a. The use of the localizer for lateral course guidance is not authorized.
b. A localizer may serve as a crossing facility where it is essential to air traffic control.
2-13. Monitoring of Navigation Facilities.
a. Monitors. It is FAA policy to provide a monitoring system for all electronic navigation facilities used in support of instrument flight procedures. Internal monitoring is provided at the facility through the use of executive monitoring equipment that causes a facility shutdown when performance deteriorates below established tolerances. A remote status indicator may also be provided through the use of a signal-sampling receiver, microwave link, or telephone circuit. VOR, VORTAC, and ILS facilities as well as new NDBs and marker beacons installed by the FAA, are provided with an internal monitoring feature. Older FAA NDBs and some 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/monitoring not available.)
(2) Category 2. Internal monitoring with status indicator at control point inoperative, but pilot reports indicate the facility is operating normally. (This is a temporary situation that requires no procedural action.)
(3) Category 3. Internal monitoring only.
(4) Category 4. Internal monitor not installed. Remote status indicator provided at control point. This category is applicable only to nondirectional beacons.
2-14. Utilization of Monitoring Categories.
a. Category 1 facilities may be used for instrument flight procedures without limitation.
b. Category 2 is a temporary condition not considered in instrument procedure development. The Air Traffic Organization is responsible for issuing Notice to Airmen (NOTAMs) on these out-of-service facilities when pilot reports indicate facility malfunction.
c. Category 3 facilities may be used in accordance with the following limitations:
(1) Alternate minimums must not be authorized if facility provides final approach course (FAC) guidance; is required for procedure entry; is used to define the final approach fix (FAF); or is used to provide missed approach guidance. See also paragraph 8-53b.
(2) Consider denying or adjusting terminal routes that require reception of succeeding Category 3 facilities to avoid obstacles.
(3) Dogleg airways or routes must not be predicated on these facilities.
(4) Navigational fixes developed from crossing radials of Category 3 facilities must not be used to break a minimum en route altitude (MEA) to higher MEA (can be used as a break to a lower MEA).
d. Category 4 facilities may be used in accordance with the following limitations:
(1) Alternate minimums may be authorized when the remote status indicator is located in an FAA ATC facility, and then only during periods the control point is attended.
(2) If the control point is other than an FAA facility, a written agreement must exist whereby an ATC facility is notified of indicated changes in facility status.
Note: Failure of this Category 4 status indicator or closure of the control point will render the facility and the approach procedure unusable during the outage.
2-15. Utilization of 75 MHz Markers. The 75 MHz markers may be used as the sole source of identification with the following limitations:
a. Missed Approach Point (MAP). Markers may be authorized as missed approach points for nonprecision approaches, provided a remote status indicator (RSI) is installed at an ATC facility.
b. Final Approach Fix. As a non-precise final approach fix, the marker must be monitored if alternate minimums are authorized. The marker need not have an RSI if collocated with a compass locator with a remote status indicator.
c. Course Reversals. Procedure turns and holding must not be authorized from a 75 MHz marker.
d. Breaks in MEAs. The 75 MHz markers must NOT be used to define the point where an en route climb to a higher altitude is required (may be used as a break to a lower altitude).
e. DP Turn Points. The 75 MHz markers must not be used to identify turn points on departure procedures. See Order 8260.46, Departure Procedure (DP) Program, paragraph 2-1.
Section 5. Implementing Epoch Year Magnetic Variation (MV)
2-16. 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, is the source for magnetic variation (MV) information and tools for establishing magnetic variation. Changing values for MV are tabulated and published on a 5-year epoch basis; e.g., 00, 05, 10, 15, 20, etc. In order to assist in stabilizing the 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. It should also be noted that there is a problem that persists in characterizing magnetic declination when airborne equipment (RNAV) applies the magnetic variation from the local NAVAID or computes the magnetic variation dynamically and applies it to a computed course or desired track.
b. Participating Offices. Management and control of Epoch Year MV values require action by the following offices:
(1) AeroNav Products.
(2) Military Organizations.
(3) National Flight Data Center (NFDC).
(4) Western, Central, and Eastern Technical Operations.
(5) Western, Central, and Eastern OSG-FPTs.
(6) Regional Airports Divisions.
2-17. Responsibilities.
a. AeroNav Products.
(1) Publish isogonic lines or segments on appropriate aeronautical charts based on current Epoch Year values.
(2) Revise en route aeronautical charts and Airport/Facility Directives (AFDs) to reflect revised MV assignments to navigation facilities in accordance with information published in the National Flight Data Digest (NFDD).
(3) Revise en route charts to apply yearly MV change values to RNAV (“Q” and “T”) route Magnetic Reference Bearings (MRB) during the first airspace charting cycle of each calendar year.
(4) Function as the focal point for all information relating to application of MV to the following elements of the NAS: navigational aids, airports, instrument flight procedures; and for coordination and liaison between AeroNav Products and the applicable Air Traffic Service Area Operations Support Group, Flight Procedure Teams (OSG-FPTs). The OSG-FPTs will coordinate with the Regional Airports and Air Traffic offices with respect to matters pertaining to change in navigational aid or airport MV of Record and its effect on instrument flight procedures.
(5) Function as the focal point for FAA and all NAS Facilities flight inspection coordination. Terminal facilities (other than VOR, VOR/DME, TACAN, VORTAC, and radar systems) do not require flight inspection of MV changes.
(6) Determine whether NOTAM action is necessary when required procedural adjustment action or MV change is not accomplished by the effective date of amended instrument procedures or revised en route charts.
(7) For FAA and all NAS Facilities, assign and maintain MVs of Record for navigational facilities and airports in whole degree increments. MVs of Record are available in the AIRNAV facility database. For new or relocated facilities, and new or revised instrument procedures, apply the appropriate MV. Analyze each facility identified as a candidate for revised MV assignment to determine if facility rotation and/or re-designation of radials are required.
(8) Establish a process to record the assigned magnetic variation and epoch year of navigational aids and airports by geographical location and the projected MV for the next Epoch Year. The process must also include the ability to identify those candidate navigational aids and airports with a difference of two degrees or more between the MV of Record and the nearest future Epoch Year value.
Continue reading ↓ 120 of 727 passages shown