Radar Vectors
FAA Order Cancelled Issued Aug 20, 2009 AFS-420 147 pages Copy saved Nov 18, 2026

Order 8260.46D Departure Procedure (DP) Program

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

Official source ↗ Open PDF

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

Distribution: Electronic Only Initiated By: AFS-400

CHANGE U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

8260.46D CHG 3

National Policy

Effective Date:

12/31/2012

SUBJ: Departure Procedure (DP) Program 1. Purpose. This order provides policy, guidance, and standardization for initiating, developing, processing, and managing the Departure Procedure program. 2. Who this change affects. The primary audience for this Order is AeroNav Products, who have the responsibility to develop instrument departure procedures and other instrument flight procedure (IFP) providers. The secondary audience includes other Air Traffic Organization (ATO) Service Area offices and 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. 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. 5.

FEDERAL AVIATION ADMINISTRATION

Explanation of changes. a. Chapter 1. Added guidance on timeline for implementation of changes. b. Chapter 2. (1) Paragraph 2-1b(11). Revised guidance to require a note be established to inform the pilot to obtain approval from ATC with their IFR clearance when executing the VCOA. (2) Paragraph 2-1b(13). Expanded guidance to better control opting-out of publishing a VCOA at locations where they are needed. (3) Paragraph 2-1d(2). Added climb gradient limit for helicopter procedures. (4) Paragraph 2-1d(6) (Added). Added statement that “Except for departures that use Radar vectors to join RNAV routes, RNAV departure procedures must only serve one airport” to match appendix E, paragraph 10.

12/31/12 8260.46D CHG 3

(5) Paragraph 2-1d(7) (Added). Added statement to prohibit multiple departure courses initially on departure and different equipment requirements; separate procedure must be established when this would be required. (6) Paragraph 2-1e(1). Expanded “Charting Altitudes” guidance to address limitations associated with publishing minimum, maximum, and mandatory altitudes. This guidance was previously addressed in Appendix D, Section 2, and Appendix E, Section 1, and has now been consolidated into this paragraph.

(7) Paragraph 2-1e(2). Clarified climb gradient application and requirements. (8) Paragraph 2-1h (Added). Added reference to Diverse Vector Area (DVA). (9) Paragraph 2-2a(3). Added guidance for when canceling a DVA. (10) Paragraph 2-2c(11). Added responsibility for ATC to collaborate with AFS-470 when an Attention All Users Page (AAUP) is necessary for RNAV departure procedures. (11) Paragraph 2-2d(2). Deleted reference to FPT OE/AAA responsibilities and made editorial changes for clarity. OE/AAA responsibilities are defined in Order 8260.19, Chapter 5, Section 1. (12) Paragraph 2-2e. Inserted a new subparagraph 4 to indicate AeroNav Products responsibility for DVA development and renumbered paragraphs that followed. (13) Paragraph 2-2g(10) Added. Added requirement for NFDC to process Form 8260- 15E (AAUP) when provided. (14) Paragraph 2-5a. Added “standard takeoff minimums.” (15) Paragraph 2-5a(4). Added Form 8260-15D to document DVA. (16) Paragraph 2-5a(5). Added Form 8260-15E to document AAUP. (17) Paragraph 2-6 (added). Added guidance to define amendment process for departure procedures. c. Appendix A. (1) Paragraph 1k(2). Deleted references to “(ATC)” annotated altitudes. (2) Paragraph 1l. Added standard climb gradient for helicopters and replaced “ATC” with “crossing” as these altitude requirements may not be solely ATC driven. (3) Paragraph 2d. Added RNP references and editorial changes.

12/31/12 8260.46D CHG 3

(4) Paragraph 2e. Editorial changes. (5) Paragraph 2f. Editorial changes and added paragraph reference for amendment process. (6) Paragraph 5b. Added altitude limitations to VA leg type guidance and editorial changes. (7) Paragraph 5d. Removed guidance that pointed to the application of criteria levels specified in Order 8260.44. Paragraph e now becomes paragraph d, Chart Annotation.

(8) Paragraph 5d. Editorial changes made within the paragraph and added RNP Departure guidance.

d. Appendix B. (1) Paragraph 5. Editorial change to clearly define when a specific frequency must be specified for charting. (2) Worksheet on page B-5, paragraph 5. Editorial change to clearly define when a specific frequency must be specified for charting. e. Appendix D. (1) Section 1, paragraph 4. Last sentence changed to have Regional Flight Standards Division, NextGen Branch (RNGB) enter the effective date for Special procedures.

(2) Section 1, paragraph 6c(2). Editorial clarification. (3) Section 1, paragraph 7a(7). Deleted. Moved VCOA information to a new paragraph 8 devoted to VCOA documentation. (4) Section 1, paragraph 8 (New). Created independent paragraph for VCOA. (5) Section 1, paragraph 9a. Added paragraph reference. (6) Section 1, paragraph 10a. Added guidance for documenting when there is more than one controlling obstacle and describe which entity each applies too. (7) Section 1, paragraph 10b. Changed “TERRAIN” to “ANTENNA.” (8) Section 1, paragraph 12. Editorial change and added “validation.” (9) Section 1, paragraph 13. Added guidance for other instrument flight procedure (IFP) providers.

12/31/12 8260.46D CHG 3

(10) Section 1, paragraph 14. Added guidance for other instrument flight procedure (IFP) providers and added “the manager” to last sentence. (11) Section 1, paragraph 18c. Added text for clarity. (12) Section 2, paragraph 1f. Last sentence changed to have Regional Flight Standards Division, NextGen Branch (RNGB) enter the effective date for Special procedures. (13) Section 2, Paragraph 3. Added guidance to describe when “thence” is used in a departure route description. (14) Section 2, paragraph 3a. Removed “(ODP/SID)” and added an example for an “at or below” altitude. (15) Section 2, paragraph 3b. Revised paragraph under the title of “Altitude restrictions requested by ATC (not authorized for ODPs)” and revised subparagraphs on this subject. These subparagraphs provide guidance on what to do when faced with ATC requests for crossing altitudes to meet local operational needs. Deleted requirement that mandated an “at or above” altitude whenever an “at or below” altitude was established for ATC operational needs. Moved remaining guidance to paragraph 2-1e(1). (16) Section 2, paragraph 5a. Corrected paragraph reference.

(17) Section 2, paragraph 5d. Removed all references to ATC climb gradient. (18) Section 2, paragraph 7a. Added guidance for documenting when there is more than one controlling obstacle and describe which entity each applies too. (19) Section 2, paragraph 7b. Changed “TERRAIN” to “ANTENNA.” (20) Section 2, paragraph 11. Editorial change to clearly define when a specific frequency must be specified for charting. (21) Section 2, paragraph 12. Editorial changes. (22) Section 2, paragraph 13. Inserted Remarks guidance to match what already appears in Remarks guidance for Form 8260-15A. (23) Section 2, paragraph 14. Editorial change and added “validation.”

(24) Section 2, paragraph 15. Added guidance for other instrument flight procedure (IFP) providers. (25) Section 2, paragraph 16. Added guidance for other instrument flight procedure (IFP) providers and added “the manager” to last sentence.

12/31/12 8260.46D CHG 3

f. Appendix E. (1) Section 1, paragraph 1f. Last sentence changed to have Regional Flight Standards Division, NextGen Branch (RNGB) enter the effective date for Special procedures. (2) Section 1, Paragraph 3. Added guidance to describe when “thence” is used in a departure route description.

(3) Section 1, paragraph 3a. Removed “(ODP/SID)” and added an example for an “at or below” altitude.

(4) Section 1, paragraph 3b. Revised paragraph under the title of “Altitude restrictions requested by ATC (not authorized for ODPs)” and revised subparagraphs on this subject. These subparagraphs provide guidance on what to do when faced with ATC requests for crossing altitudes to meet local operational needs. Deleted requirement that mandated an “at or above” altitude whenever an “at or below” altitude was established for ATC operational needs. Moved remaining guidance to paragraph 2-1e(1).

(5) Section 1, paragraph 5d. Removed all references to ATC climb gradient. (6) Section 1, paragraph 7a. Added guidance for documenting when there is more than one controlling obstacle and describe which entity each applies too.

(7) Section 1, paragraph 7b. Changed “TERRAIN” to “ANTENNA.” (8) Section 1, paragraph 10. Editorial change to replace “RDVA” with proper terms and replaced “may” with “must.” (9) Section 1, paragraph 11. Editorial change to clearly define when a specific frequency must be specified for charting. (10) Section 1, paragraph 13. Inserted Remarks guidance to match what already appears in Remarks guidance for Form 8260-15A.

(11) Section 1, paragraph 14. Editorial change and added “validation.” (12) Section 1, paragraph 15. Added guidance for other instrument flight procedure (IFP) providers. (13) Section 1, paragraph 16. Added guidance for other instrument flight procedure (IFP) providers and added “the manager” to last sentence. (14) Section 1, figure E-3. Added speed restriction to sample Form. (15) Section 3 (Added). Added Instructions and sample Form for completing RNAV departure procedure Attention All Users Page (AAUP).

12/31/12 8260.46D CHG 3

g. Appendix F. Appendix created to provide guidance for processing Helicopter RNAV departure procedures from VFR heliports and sample forms. h. Appendix G. Appendix is now “Instructions for Completing Form 8260-15D.” This was moved from Order 8260.56, Diverse Vector Area (DVA) Evaluation, appendix B, without any changes made to content. i. Appendix H.

(1) The former Appendix G has now become Appendix H. (2) Revised VCOA definition to match definition in Pilot/Controller Glossary. AFS-1 signature

12/31/12 8260.46D CHG 3

PAGE CHANGE CONTROL CHART

PAGE CHANGE CONTROL CHART

Remove Pages Dated Insert Pages Dated i thru ii 04/14/11 i thru ii 12/31/12 1-1 thru 1-2 04/14/11 1-1 thru 1-2 12/31/12

2-1 thru 2-2 04/14/11 2-1 thru 2-2 12/31/12

2-3 thru 2-16 09/30/11 2-3 thru 2-18 12/31/12

A-1 thru A-6 04/14/11 A-1 thru A-6 12/31/12

A-7 thru A-10 09/30/11 A-7 thru A-10 12/31/12

B-1 thru B-2 04/14/11 B-1 thru B-2 12/31/12

B-5 thru B-6 08/20/09 B-5 thru B-6 12/31/12

D-1 thru D-16 04/14/11 D-1 thru D-16 12/31/12

D-17 thru D-22 09/30/11 D-17 thru D-22 12/31/12

D-23 thru D-24 04/14/11 D-23 thru D-24 12/31/12

D-25 thru D-26 09/30/11 D-25 thru D-28 12/31/12

E-1 thru E-2 09/30/11 E-1 thru E-2 12/31/12

E-5 thru E-8 09/30/11 E-5 thru E-8 12/31/12

E-9 thru E-10 04/14/11 E-9 thru E-10 12/31/12

E-11 thru E-14 09/30/11 E-11 thru E-14 12/31/12

E-17 thru E-18 08/20/09 E-17 thru E-18 12/31/12

E-19 thru E-20 04/14/11 E-19 thru E-20 12/31/12

E-27 thru E-28 09/30/11 E-27 thru E-28 12/31/12

NEW E-33 thru E-36 12/31/12

F-1 thru F-2 08/20/09 F-1 thru F-10 12/31/12

G-1 thru G-6 04/14/11 G-1 thru G-6 12/31/12

NEW H-1 thru H-6 12/31/12

THIS PAGE IS INTENTIONALLY LEFT BLANK

THIS PAGE IS INTENTIONALLY LEFT BLANK

Distribution: Electronic Only Initiated By: AFS-400

CHANGE U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

8260.46D CHG 2

National Policy

Effective Date:

09/30/11

SUBJ: Departure Procedure (DP) Program 1. Purpose. This order provides policy, guidance, and standardization for initiating, developing, processing, and managing the Departure Procedure program. 2. Who this change affects. The primary audience for this Order is AeroNav Products, who has the responsibility to develop instrument departure procedures. The secondary audience includes other Air Traffic Organization (ATO) Service Area offices and Flight Standards headquarters and regional office Divisions/Branches. 3. Where You Can Find This Order. You can find this order on the Federal Aviation Administration’s (FAA) Web site at http://www.faa.gov/regulations_policies/orders_notices. 4. Explanation of changes. a. Chapter 2. (1) Paragraph 2-1b(13). Editorial change to indicate VCOA is not mandatory at airport where ATC cannot allow the maneuver. Also added statement to say that Form 8260-15B will contain this information when the ODP is in a graphic. (2) Paragraph 2-1e. Revised guidance on documenting crossing altitudes. (3) Paragraph 2-1e(2).

FEDERAL AVIATION ADMINISTRATION

Revised paragraph to support the revision of paragraph 2-1e(1) that eliminates the need to differentiate between climb gradients for either ATC purposes or obstacle clearance. There is no way to determine if the altitude depicted on the chart is for obstacle clearance or to meet an ATC requirement; therefore, the crossing altitude/climb gradient must be complied with unless ATC intervenes and assumes responsibility for obstacle avoidance. (4) Paragraph 2-2e(12). Added requirement to include “T” symbol on SIDs and clarified in the Note that the “T” symbol will not be placed on graphic ODPs. b. Appendix A. Paragraph 5e(5) examples. Revised graphics for “Elemo Two Departure,” “Micky Four Departure,” “Shemp One Departure (RNAV),” and “Shemp Two Departure (RNAV)” to support text revisions. c. Appendix D.

09/30/11 8260.46D CHG 2

(1) Section 2, Paragraph 3. Revised guidance on documenting crossing altitudes. (2) Section 2, Paragraph 4i. Removed “(ATC)” reference. (2) Section 2, Figure D-7. Revised FAA Form 8260-15B for “Micky Four Departure,” to support revised application guidance. d. Appendix E. (1) Section 1, Paragraph 3. Revised guidance on documenting crossing altitudes. (2) Section 1, Paragraph 4i, Removed “(ATC)” reference. (3) Section 1, Figure E-2. Revised FAA Form 8260-15B for “Shemp One Departure (RNAV),” to support revised application guidance. (4) Section 1, Figure E-3. Revised FAA Form 8260-15B for “Shemp Two Departure (RNAV),” to support revised application guidance. (5) Section 2, Paragraph 1h. Modify paragraph to allow use of block altitudes.

(6) Section 2, Figure E-7. Revised FAA Form 8260-15C for “Shemp Two Departure (RNAV),” to support revised application guidance.

PAGE CHANGE CONTROL CHART Remove Pages Dated Insert Pages Dated Chapter 2 Chapter 2 2-3 thru 2-16 04/14/11 2-3 thru 2-16 09/30/11 Appendix A Appendix A A-7 thru A-8 04/14/11 A-7 thru A-8 09/30/11

Appendix D Appendix D D-17 thru D-22 04/14/11 D-17 thru D-22 09/30/11 D-25 thru D-26 04/14/11 D-25 thru D-26 09/30/11

Appendix E Appendix E E-1 thru E-8 04/14/11 E-1 thru E-8 09/30/11 E-11 thru E-14 04/14/11 E-11 thru E-14 09/30/11 E-21 thru E-30 04/14/11 E-21 thru E-30 09/30/11

AFS-1 signature

Distribution: Electronic Only Initiated By: AFS-400

CHANGE U.S. DEPARTMENT OF TRANSPORTATION

CHANGE U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

8260.46D CHG 1

National Policy

Effective Date:

04/14/11

SUBJ: Departure Procedure (DP) Program 1. Purpose. This order provides policy, guidance, and standardization for initiating, developing, processing, and managing the Departure Procedure program. 2. Who this change affects. The primary audience for this Order is AeroNav Services, who have the responsibility to develop instrument departure procedures. The secondary audience includes other Air Traffic Organization (ATO) Service Area offices and Flight Standards headquarters and regional office Divisions/Branches. 3. Where Can I Find This Notice? Inspectors can access this order through the Flight Standards Information Management System (FSIMS) at http://fsims.avs.faa.gov. Operators may find this information on the Federal Aviation Administration’s (FAA) Web site at http://www.faa.gov/library/manual/examiners_inspectors/8000. 4. Explanation of changes. a. General. Changed reference from National Flight Procedures Office (NFPO) and National Aeronautical Charting Office (NACO) to AeroNav Products. b. Chapter 1. Editorial correction. Removed incorrect paragraph change references from paragraph 1-6o and 1-6t. Remaining paragraphs re-lettered. c. Chapter 2. (1) Paragraph 2-1b(2). Revised to “Do not publish text that allows an option to use a SID or alternate maneuver assigned by ATC; e.g., “Climb runway heading to 1200 before turning or use Manchester Departure” or “Turn right, climb direct ABC VOR or as assigned by ATC.”” (2) Paragraph 2-1b(11). Added “When a Visual Climb Over Airport (VCOA) has been established, a note must be established that requires the pilot to inform ATC prior to departure when executing the VCOA.”

FEDERAL AVIATION ADMINISTRATION

04/14/11 8260.46D CHG 1

(3) Paragraph 2-1b(14). Added “Textual ODPs may be designed to terminate at a fix/NAVAID located within the IFR en route structure and/or at an altitude that will allow random (diverse) IFR flight.” (4) Table 1. Editorial. (5) Paragraph 2-1c(2). Deleted guidance Diverse Vector Area and split paragraph 2- 1c(1) into two paragraphs, making the second sentence the new paragraph 2-1c(2). (6) Paragraph 2-1e(1)(a). Added “amended/” prior to cancelled to make it clear that ATC can also amend an altitude that is annotated with “(ATC)” adjacent to the number.

(7) Paragraph 2-2a(1) & (2). Introduced the Service Area Operations Support Group (OSG), Flight Procedures Team (FPT) as part of process to establish/modify SIDs.

(8) Paragraph 2-2c(6) and 7. Removed paragraphs. Environmental Requirements are addressed in other FAA directives and guidance not required in this order.

(9) Paragraph 2-2c. Switched order of sub-paragraphs 6 and 7, and removed the Note from the new sub-paragraph 6.

(10) Paragraph 2-2c(12). Deleted. RAPT and/or ATC facility does not distribute these. (11) Paragraph 2-2d. Renamed paragraph to “Service Area Flight Procedures Office”

(11) Paragraph 2-2d(5). Modified text to correspond with paragraph 2-2e(7).

(12) Paragraph 2-2e(4). Editorial change to show Service Area OSG is responsible for DME/DME screening.

(13) Paragraph 2-2e(7). Editorial change to show distribution responsibility and correspond with paragraph 2-2d(5). (14) Paragraph 2-2f added, following paragraph up-lettered. Added Aviation System Standards responsibilities. (15) Paragraph 2-4b. Changed second sentence to reflect correct ATO responsibility. d. Appendix A. (1) Paragraph 1f. Changed sentence to refer to “Graphic ODPs” only. (2) Table A-1. Changed Table notes 2 to state “VA (Heading-to-an-altitude) may only be used as the first leg of a departure and must be followed by a DF leg.” (3) Paragraph 5e(5). Changed to state “Except as required by paragraph 2-1f(3), all.”

04/14/11 8260.46D CHG 1

(4) Paragraph 5e(5) examples. Revised graphics for “Shemp One Departure (RNAV)” and “Shemp Two Departure (RNAV)” to support text revisions. e. Appendix C. (1) Instructions updated to included guidance for updating “Fix Use” when applicable. f. Appendix D. (1) Section 1, paragraph 1. Emphasized “If all runways are standard…” and added “(e.g., no ODP required).” (2) Section 1, Paragraph 6. Editorial, corrected paragraph reference. (3) Section 1, Paragraph 7a(1). Changed to “HEADING 350.11.” (4) Section 1, Paragraph 7a(7). Added “Additionally, the statement “Notify ATC prior to executing VCOA” must be included at the end.” (5) Section 1, Paragraph 8b. Added “0.1 NM.” (6) Section 1, Paragraph 10. Added “Remarks” block and reference to Order 8260.19 paragraph 8-71g, requiring a chart note when ODP is a Special. Updated figures D-1 thru D-5. (7) Section 2, Paragraph 3b, Note 1. Added “(or required nonstandard “minimum” climb gradient).” (8) Section 2, Paragraph 6b. Added “0.1 NM.” (9) Figure D-2. Updated, added “When Executing VCOA, Notify ATC Prior to departure.” (10) Figure D-6. Updated, added visibility value and “When Executing VCOA, Notify ATC Prior to Departure.” g. Appendix E. (1) Section 1, Paragraph 3b, Note 1. Added “(or required nonstandard “minimum” climb gradient).” (2) Section 1, Table E-1. Removed “altitude” and accompanying asterisk reference. (3) Section 1, paragraph 3e, Examples. Removed example that showed a altitude in conjunction with a VI leg followed by a CF leg.

04/14/11 8260.46D CHG 1

(4) Section 1, Paragraph 5a. Added reference to Order 8260.19 paragraph 8-71g, requiring a chart note when ODP is a Special. (5) Section 1, Paragraph 6b. Added “0.1 NM.” (6) Section 2, Paragraph 4b(3). Removed ability to develop procedures using VA/CF leg type combination. h. Appendix G. Removed National Aeronautical Charting Office (NACO) and National Flight Procedures Office (NFPO) definitions from paragraph 3u and 3b. Remaining paragraphs re-lettered.

PAGE CHANGE CONTROL CHART Remove Pages Dated Insert Pages Dated Table of Contents Table of Contents i and ii 08/20/09 i and ii 04/14/11

Chapter 1 Chapter 1 1-1 thru 1-4 08/20/09 1-1 thru 1-4 04/14/11

Chapter 1 Chapter 1 1-1 thru 1-4 08/20/09 1-1 thru 1-4 04/14/11

Chapter 2 Chapter 2 2-1 thru 2-16 08/20/09 2-1 thru 2-16 04/14/11

Appendix A Appendix A A-1 thru A-8 08/20/09 A-1 thru A-8 04/14/11

Appendix B Appendix B B-1 thru B-2 08/20/09 B-1 thru B-2 04/14/11

Appendix C Appendix C C-1 thru C-2 08/20/09 C-1 thru C-2 04/14/11

Appendix D Appendix D D-1 thru D-28 08/20/09 D-1 thru D-28 04/14/11

Appendix D Appendix D D-1 thru D-28 08/20/09 D-1 thru D-28 04/14/11

Appendix E Appendix E E-1 thru E-6 08/20/09 E-1 thru E-6 04/14/11 E-9 thru E-16 08/20/09 E-9 thru E-16 04/14/11 E-19 thru E-26 08/20/09 E-19 thru E-26 04/14/11

Appendix G Appendix G G-1 thru G-6 08/20/09 G-1 thru G-6 04/14/11 AFS-1 signature

Appendix G Appendix G G-1 thru G-6 08/20/09 G-1 thru G-6 04/14/11 AFS-1 signature

12/31/12 8260.46D CHG 3 TABLE OF CONTENTS Paragraph Page Chapter 1. General Information

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

2-1. Departure Procedure Guidelines ------------------------------------------------------- 2-1 2-2. Responsibilities-------------------------------------------------------------------------- 2-10 2-3. Accuracy Verification and Responsibilities ----------------------------------------- 2-14 2-4. Military Departure Procedures -------------------------------------------------------- 2-14 2-5. FAA 8260-15 Series Forms------------------------------------------------------------ 2-15 2-6. Procedure Amendments ---------------------------------------------------------------- 2-17 Appendix A. Guidelines for the Design of Graphic Instrument Departure Procedures (DPs) (Pages 1-10) Appendix B. Instructions for Completing Graphic Departure Procedure (DP) Requirements Worksheet (Pages 1-8) Appendix C. Instructions for Completing FAA Form 8260-2, Data Worksheet (Pages 1-4) Appendix D. Instructions for Completing FAA Form 8260-15A, Takeoff Minimums and Obstacle Departure Procedures (ODP) and Sample Forms (Pages 1-16) Instructions for Completing FAA Form 8260-15B, Graphic Departure Procedure (DP) [Non-RNAV Departure Procedures] and Sample Forms (Pages 17-28) Appendix E. Instructions for Completing FAA Form 8260-15B, Graphic Departure Procedures (DPs) [RNAV and RNP Departure Procedures] and Sample Forms (Pages 1-20) Instructions for Completing FAA Form 8260-15C, Departure (Data Record) and Sample Forms (Pages 21-32) Instructions for Completing FAA Form 8260-15E, RNAV Departure Procedure Attention All Users Page (AAUP) [RNAV Departure Procedure] and Sample Forms (Pages 33-36)

i

12/31/12 8260.46D CHG 3

ii

TABLE OF CONTENTS (Continued) Paragraph Page Appendix F. Helicopter RNAV Departure Procedures 1. General------------------------------------------------------------------------------- F-1 2. Departure Procedure --------------------------------------------------------------- F-1 3. Documentation---------------------------------------------------------------------- F-2 Appendix G. Instructions for Completing FAA Form 8260-15D.

1. Documentation--------------------------------------------------------------------- G-1 Appendix H. Administrative Information

1. Distribution------------------------------------------------------------------------- H-1 2. Background------------------------------------------------------------------------- H-1 3. Definitions-------------------------------------------------------------------------- H-1 4. Related Publications--------------------------------------------------------------- H-4 5. Forms and Reports ---------------------------------------------------------------- H-5 6. Information Update---------------------------------------------------------------- H-6

12/31/12 8260.46D CHG 3

Chapter 1. General Information

Chapter 1. General Information

1-1. Purpose of This Order. This order provides policy, guidance, and standardization for initiating, developing, processing, and managing the DP program. 1-2. Audience. The primary audience for this Order is AeroNav Products employees, who have the responsibility to develop instrument departure procedures. The secondary audience includes other Air Traffic Organization (ATO) Service Area offices and Flight Standards headquarters and regional office Divisions/Branches. 1-3. Where You Can Find This Order. This Order can be found on the Directives Management System (DMIS) Web site at https://employees.faa.gov/tools_resources/orders_notices. This Order is available to the public at http://www.faa.gov/regulations_policies/orders_notices. 1-4. What this Order Cancels. Order 8260.46C, Departure Procedure (DP) Program, dated August 5, 2005. 1-5. 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-6. Explanation of Changes. a. General. Formatting revised to meet current Federal Aviation Administration (FAA) standards. Paragraphs are re-aligned for better editorial flow. b. Paragraph 2-1a(1). Text added to clarify Terminal Instrument Procedures (TERPS) application of diverse departure criteria analysis. c. Paragraph 2-1b. Paragraph revised and expanded to include all items unique to obstacle departure procedures (ODPs). d. Paragraph 2-1b(1). Emphasizes the primary goal in ODP development. e. Paragraph 2-1b(12). Deletes the requirement for mandatory Visual Climb Over Airport (VCOA) development at high density airports where Air Traffic Control (ATC) will not allow the maneuver. f. Table 2-1. VCOA note moved to paragraph 2-1b(11).

g. Paragraph 2-1c. Paragraph expanded to include all items unique to standard instrument departures (SIDs). h. Paragraph 2-1c(2). Specifies that a Diverse Vector Area (DVA) must be established when ATC desires to use radar vectors to establish aircraft on published SIDs.

04/14/11 8260.46D CHG 1

i. Paragraph 2-1d(2)(a). Adds requirement for supporting documentation when requesting Flight Standards approval for excessive climb gradients. j. Paragraphs 2-1d(2)(b) and (c). Previously published notes now included as separate sub-paragraphs. k. Paragraph 2-1d(3). Adds policy for DP speed restrictions. l. Paragraph 2-1e(1). Provides guidance for charting minimum altitude restrictions (obstacle clearance and ATC) for both ODPs and SIDs. m. Paragraph 2-1e(2). Provides guidance for charting required climb gradients (obstacle clearance and ATC) for both ODPs and SIDs. n. Paragraph 2-1e(3). Provides guidance for charting speed restrictions (obstacle clearance and ATC) for both ODPs and SIDs. o. Paragraph 2-1f(3). Adds DVA requirements for radar SIDs at runways that failed the TERPS diverse departure analysis. p. Paragraph 2-1g(6). Adds guidance regarding use of the word “immediate/ immediately.” q. Paragraph 2-2c(9). Requires the ATC facility providing departure control service to coordinate graphic DP name and computer code with the servicing ARTCC as specified in appendix A. r.

Paragraph 2-2g. National Aeronautical Charting Office (NACO) Responsibilities added. s. Paragraph 2-3c. Requires notification of NACO for chart correction FDC NOTAMs. t. Paragraph 2-5a(1)(e). Requires DVA information to be documented on Form 8260-15A. u. Paragraph 2-5c. Requires supporting documentation when requesting Flight Standards approval. v. Appendix A, paragraph 1j. Speed restriction policy re-located to paragraph. w. Appendix A, table A-1 and paragraph 5b footnote 1. Added VI leg type. x. Appendix A, paragraph 5e. Replaced TYPE A/B designations with RNAV-1 and added RNP-1 DP guidance. y. Appendix B. Changed “Block” to “Line” and minor editorial changes. z. Appendix C. Changed “Block” to “Line” and minor editorial changes. aa. Appendix D. Modifies Forms 8260-15A and 8260-15B and revises completion instructions accordingly. Also, deleted FAA Form 8260-15D, Departure Procedure (Continuation).

04/14/11 8260.46D CHG 1

bb. Appendix D, Section 1, paragraph 8a. Note added to provide guidance for AAO use. cc. Appendix D, Section 1, figures D-1 through D-5. Sample report format forms inserted.

dd. Appendix D, Section 2, paragraph 6a. Note added to provide guidance for AAO use. ee. Appendix E. Deleted FAA Form 8260-15D, Departure Procedure (Continuation). Modifies Form 8260-15B and revises completion instructions accordingly. ff. Appendix E, Section 1, paragraph 3b. Adds clarification that direction of turn is only required for DF legs when the course change exceeds 15 degrees. gg. Appendix E, Section 1, paragraph 3d and table E-1. VI leg capability added. hh. Appendix E, Section 1, paragraph 6. Note added to provide guidance for AAO use. ii. Appendix E, Section 2. Updated instructions to include VI legs. jj. Appendix F. Prepared and Reserved Helicopter Departure Procedure to be established at a later time. kk. Appendix G, paragraph 2. Functional area distribution codes and responsibilities are updated to reflect organizational changes. ll. Appendix G, paragraph 3k. Diverse Vector Area definition added. mm. Appendix G, paragraph 4kj. Added reference to Order 8260.53, Standard Instrument Departures that Use Radar Vectors to Join RNAV Routes.

1-3 (and 1-4)

THIS PAGE IS INTENTIONALLY LEFT BLANK

12/31/12 8260.46D CHG 3

Chapter 2. Responsibilities 2-1. Departure Procedure (DP) Guidelines. a. General. There are two types of DPs; those developed to assist pilots in obstruction avoidance, referred to as Obstacle Departure Procedure (ODP), and those developed to communicate air traffic control clearances, referred to as Standard Instrument Departure (SID). (1) A diverse departure assessment must be conducted for those airports with approved instrument approach procedures. ODPs are developed by AeroNav Products at locations where they have instrument procedure development responsibility. (2) ODPs may also be required at private airports where the FAA does not have instrument procedure development responsibility. It is the responsibility of non-FAA proponents to ensure a TERPS Diverse Departure obstacle assessment has been accomplished and an ODP developed, where applicable. b. Obstacle Departure Procedures. An ODP and/or non-standard takeoff minimums must be developed when obstructions penetrate the 40:1 departure obstacle clearance surface (OCS) as described in Order 8260.3, Volume 4.

THIS PAGE IS INTENTIONALLY LEFT BLANK

Use table 2-1 as a guide to determine each situation and the required action. The following rules apply to ODPs: (1) The primary goal in ODP development is to retain standard takeoff minimums with standard climb gradient to the extent possible. See table 2-1 for recommended ODP development combinations. (2) Establish only one ODP for a Runway. This will be considered the default instrument flight rule (IFR) departure procedure for a given runway and is intended for pilot awareness and use in the absence of ATC radar vectors or SID assignment. Do not publish text that allows an option to use a SID or alternate maneuver assigned by ATC; e.g., “Climb runway heading to 1200 before turning or use Manchester Departure” or “Turn right, climb direct ABC VOR or as assigned by ATC. (3) When using table 2-1, apply “before rounding” values to each situation to determine required action. (4) An ODP may be either textually or graphically depicted within the following guidelines. (a) Textual ODP.

A relatively simple ODP may be published textually unless a graphical depiction is required for clarity. Textual ODP instructions that exceed a maximum of one turn, one altitude change, and one climb gradient must be published graphically. (b) Graphic ODP. Complex ODPs are those that require a visual presentation to clearly communicate the departure instructions and desired flight paths. If the ODP is depicted graphically, it must be clearly stated on FAA Form 8260-15A, Takeoff Minimums and Textual

12/31/12 8260.46D CHG 3

Departure Procedures (DP), in the Departure Procedure section; e.g., “USE JONES DEPARTURE. The decision to graphically publish ODPs rests within AeroNav Products. When determining the need for a graphic DP, AeroNav Products must, in addition to the textual DP restrictions noted in paragraph 2-1b(4)(a), consider: 1. The number of ground-based navigational aids (NAVAIDs) and fixes. 2. Whether graphical depiction will enhance pilot comprehension of the procedure. 3. The proximity and effect of precipitous or significant terrain. (5) A graphic ODP may serve one or more runways at a single airport; e.g., a graphic departure may contain initial departure instructions for both Runways 9 and 27 on the same chart. (6) ODPs must be developed with primary emphasis given to using the least onerous route (see appendix G) to the en route structure or at an altitude that will allow random (diverse) IFR flight, while accommodating commonly used routings out of each airport to the maximum extent practicable.

Procedure designers must consider the impact on local ATC operations when using the phrases “before turning” or “before proceeding on course. ODPs must be coordinated with ATC to ensure flight safety and compatibility with the local operating environment and the en route structure. (7) ODPs may include a climb gradient when required for obstruction avoidance; however, ATC related climb gradients, speed and/or altitude restrictions must not be included in ODP development. (8) Naming conventions and computer code assignments for graphic ODPs must follow the guidance specified for SIDs in appendix A to ensure controller awareness of route flown. (9) Transition Routes are not permitted on graphic ODPs. (10) ODPs must be developed using ground based NAVAIDs, area navigation (RNAV), or dead reckoning guidance wherever possible. Radar vectors must not be specified for navigation guidance in ODP development. At those locations served by RNAV approaches exclusively, every effort must first be made to develop an ODP that accommodates conventional (preferably VOR) navigation systems.

If this effort fails, an RNAV ODP must be developed. (11) When a Visual Climb Over Airport (VCOA) has been established, publish a note that requires the pilot to obtain approval from ATC with their IFR clearance when executing the VCOA. See appendix D, section 1, paragraph 8. (12) A VCOA maneuver must not be used in conjunction with an RNAV ODP.

12/31/12 8260.46D CHG 3

(13) The VCOA requirement in table 2-1 is mandatory. However, ATC may submit a justification request to Flight Procedure Implementation and Oversight Branch (AFS-460) for Flight Standards Service (AFS) approval to opt-out of publishing a VCOA. This “opt-out” option is intended for use at major metropolitan airports that experience a high volume of traffic (e.g., Los Angeles, San Francisco, New York, etc.) where permission to use a VCOA is impractical and/or impossible. ATC must consider user needs as well as the operational impact upon low performance aircraft that must depart IFR from mountainous/obstacle encumbered airports when deciding to submit a request to not establish a VCOA. (14) Textual ODPs may be designed to terminate at a fix/NAVAID located within the IFR en route structure and/or at an altitude that will allow random (diverse) IFR flight. (15) Graphic ODPs must be designed to terminate at a fix/NAVAID located within the IFR en route structure.

Table 2-1. ODP Development Combinations

SITUATION ACTION

SITUATION ACTION

1) TERPS diverse departure obstacle assessment does not identify any obstacle penetrations.

Complete Form 8260-15A documenting standard takeoff minimums apply.

2) TERPS diverse departure obstacle assessment identifies obstacles within the initial climb area (ICA) that require a CG greater than 200 ft/NM to an altitude of 200 ft or less, above Departure End of Runway (DER) (commonly referred to as “low, close-in obstacles”).

Establish a DP that provides the pilot a NOTE identifying the obstacle(s) type, location relative to DER, height (AGL), and elevation (MSL). See appendix D for recommended publication text available.

3) TERPS diverse departure obstacle assessment identifies obstacles that require a CG greater than 200 ft/NM, to an altitude greater than 200 ft above DER.

A) Obstacles located within the ICA [extended] 3 SM or less from DER: Establish a DP using one of the following options (listed in order of preference):

1) Publish a textual or graphic route/sector to avoid the obstacle(s) with standard takeoff minimums and standard CG, OR

2) Publish a ceiling and visibility to see and avoid the obstacle(s) with the option of standard takeoff minimums with a minimum CG to a specified fix or altitude that provides obstacle clearance with a standard CG, AND;

a) Provide a NOTE identifying the obstacle(s), which specifies the obstacle description, location relative to the DER, height (AGL), and elevation (MSL), AND

b) For obstacles that penetrate the 40:1 OCS by 35 ft or less, provide an option to reduce takeoff runway length to accommodate the most penetrating obstacle based on a standard 200 ft/NM climb gradient, OR

3) A combination of options 1) and 2) above.

12/31/12 8260.46D CHG 3

B) All Other Obstacles: Establish a DP using one of the following options (listed in order of preference):

1) Publish a graphic or textual route/sector to avoid the obstacle with standard takeoff minimums and standard climb, OR

2) Publish standard takeoff minimums with a minimum CG to a specified fix or altitude that provides obstacle clearance with a standard CG, AND

a) For obstacles that penetrate the 40:1 OCS by 35 ft or less, provide an option to reduce takeoff runway length to accommodate the most penetrating obstacle based on a standard 200 ft/NM CG, AND/OR b) Provide a ceiling and visibility sufficient to allow a visual climb over the airport (VCOA) to an altitude that will provide obstacle clearance [see paragraph 2-1b(11) and (12)], OR

3) A combination of options 1 and 2 above. C) Both Action A) and B) Obstacles:

1) If the DP highest CG is based on an obstacle  3 SM from DER (Action A), establish a DP using one of the following options (listed in order of preference):

a) Publish a graphic or textual route/sector to avoid the obstacle with standard takeoff minimums and standard climb, OR

b) Publish standard takeoff minimums and the minimum CG required to clear the  3 SM obstacle to a specified fix or altitude that will provide subsequent obstacle clearance above all DP obstacles based on a standard 200 ft/NM CG, AND

1 Provide a ceiling and visibility to see and avoid the  3 SM obstacle and the minimum CG required to clear all other obstacles outside the ICA (extended) to a specified fix or altitude that provides obstacle clearance, AND

2 For obstacles that penetrate the 40:1 OCS by 35 ft or less, provide an option to reduce takeoff runway length to accommodate the most penetrating obstacle based on a standard 200 ft/NM climb gradient, AND/OR

3 Provide a ceiling and visibility sufficient to allow a VCOA to an altitude that will provide obstacle clearance [see paragraphs 2-1b(11) and (12)],

2) If the DP highest CG is based on all other obstacles (Action B), then Action B above applies.

Note: Where a graphic route/sector is published, include on the chart: takeoff minimums, required CGs, and applicable obstacle data for each runway using the DP. D) If none of the above actions are feasible, an IFR departure must not be authorized.

4) TERPS diverse departure obstacle assessment identifies obstacles requiring a CG to 200 ft or less above DER and additional obstacles that require a CG to an altitude greater than 200 ft above DER.

Apply a combination of action items from situations 2) and 3).

12/31/12 8260.46D CHG 3

c. Standard Instrument Departures (SIDs). SIDs are developed to assist in meeting environmental, capacity, and air traffic control requirements. SIDs may be requested by specific ATC facilities, the military services, or other proponents to enhance operations. A SID also provides protection from obstacles and is depicted graphically; however, it will not contain the “(OBSTACLE)” designation following the procedure title on the chart, and may not be flown unless approved by ATC. The following rules apply to SIDs: (1) SIDs must be designed to terminate at a fix/NAVAID depicted on an IFR en route chart, at an altitude that will allow random IFR flight, or at a position and altitude where ATC radar service is provided. (2) When a SID is designed to incorporate radar vectors at the termination point, provide a heading for charting and incorporation into the avionics database in the event ATC instructions are not received prior to or at the termination fix. d. Design Constraints.

The following design constraints apply to all ODPs and SIDs: (1) DPs must not require a turn prior to reaching 400 ft above the departure end of runway (DER) elevation. See Order 8260.3, Volume 4, and Order 8260.58 when a turn is required within 2 NM of DER. (2) DPs requiring a climb gradient (CG) in excess of 500 ft/NM (600 ft/NM for helicopters), whether for obstacle clearance or air traffic control restrictions, must be approved by Flight Standards Service or appropriate DoD authority. Approval requests will be assessed by the FAA Flight Technologies and Procedures Division (AFS-400), Procedures Review Board (PRB).

Note: Consideration for approval will be based on, but not limited to, potential users/aircraft capability of meeting such a CG, and location of the obstruction along the projected flight track that is causing the CG. (a) Requests for approval of climb gradients in excess of 500 ft/NM (600 ft/NM for helicopters) must include documentation showing the calculations used to derive the climb gradient values. (b) When Flight Standards Service will not approve a climb gradient (CG) in excess of 500 ft/NM (600 ft/NM for helicopters) and all of the obstacles forcing such a CG are located inside the ICA (extended) 3 SM or less from DER, a ceiling and visibility may be applied to see and avoid the obstruction(s) as the only option available. (c) When Flight Standards will not approve a climb gradient (CG) in excess of 500 ft/NM (600 ft/NM for helicopters) and any of the obstacles forcing such a CG are located outside the ICA (extended) greater than 3 SM from DER; a stand-alone VCOA procedure may be used as the only option available for obstacle avoidance.

12/31/12 8260.46D CHG 3

(3) Speed restrictions may be specified only when absolutely necessary to ensure obstacle clearance, airspace efficiency during turns, or when necessary to achieve an operational advantage. Refer to applicable DP criteria directives. (a) ATC required speed restrictions are only allowed in SID design and must not be included in ODPs. (b) Speed restrictions [except as noted in paragraph 2-1d(3)(c)] must be limited to one restriction per fix/waypoint. In this instance, a minimum altitude based on the minimum required climb gradient must also be specified at the fix/waypoint. (c) Avoid using multiple speed restrictions at the same fix for different aircraft types, insofar as possible; e.g., “Turbo-props do not exceed 160 KIAS until passing GARVY; Turbo-jets do not exceed 230 KIAS until passing GARVY.” When multiple restrictions must be applied to support ATC operations, apply only one restriction for each aircraft type. (4) Fan markers must not be used as a fix to designate a turning point on a SID or ODP. (5) Do not establish VCOA procedures in conjunction with a SID. (6) Except for departures that use Radar vectors to join RNAV routes, RNAV departure procedures must only serve one airport. (7) Do not establish DPs containing more than one initial departure route from the end of a runway to support different types of aircraft (i.e., jet, turbo-prop, etc.) or different equipment requirements (DME, non DME). Where this is necessary, separate procedures must be developed. e. Charting Constraints. The following charting constraints apply:

(1) Charting Altitudes. Document altitudes for charting as follows: (a) Graphic departure procedures may require depiction of a minimum altitude at a fix established along the departure route. SIDs may require altitudes to support ATC requirements; however, ATC required altitudes must not be depicted on ODPs.

(b) When a minimum “at or above” altitude restriction has been requested by ATC at a fix in an initial SID routing (prior to reaching the SID termination fix) that is higher than the required procedure design minimum altitude at the same fix, the higher requested ATC altitude then becomes the minimum altitude at that fix. This altitude must support all procedure design and criteria requirements (i.e., obstacle clearance/procedure design constraints/navigation solution and the ATC requirement(s)).

(c) When an “at or below” altitude restriction at a fix has been requested by ATC, ensure that the requested altitude meets all obstacle clearance (ROC) requirements as well as other criteria design standards. ATC may also have a need to establish an “at or above” altitude

12/31/12 8260.46D CHG 3

in conjunction with the “at or below” altitude at the same fix making this either a “mandatory” or “block” fix crossing altitude. (d) When an altitude restriction is requested by ATC for a fix located on a transition route, it must be at or above the specified minimum en route altitude (MEA) for the route. (e) Enter altitudes to be charted on the appropriate 8260-15 series form (see appendix D or E). Government and civil charting organizations will chart/depict these altitudes according to their individual specifications. (2) Charting a Minimum Climb Gradient. Establish a single minimum climb gradient exceeding 200 ft/NM (400 ft/NM for helicopters) whenever required for obstruction clearance, airspace, environmental, ATC, and/or RNAV or required navigation performance (RNP) operational limitations [i.e., lateral navigation (LNAV) engagement altitude and/or distance measuring equipment (DME)/DME reception]. When a climb gradient is required to support an LNAV engagement altitude (e.g., 500 ft/NM to 1300) before turning, a reduced, second climb gradient may be established in this situation only (i.e., a maximum of two climb gradients). See applicable 8260-series Orders for the appropriate criteria to use when establishing a climb gradient. Enter minimum climb gradient(s) for charting on the appropriate 8260-15 series form (see appendix D, E, or F). (3) Charting Speed Restrictions. Required speed restrictions must be identified per Interagency Air Cartographic Committee (IACC) specifications. (a) Speed restrictions for textual ODPs will follow the departure instructions; e.g., “...climbing right turn direct XXX VOR. Do not exceed 200 KIAS until XXX VOR.”

(b) Speed restrictions for graphic ODPs will be annotated on the chart at the restriction point. (c) ATC SID speed restrictions will be identified by placing “(ATC)” at the end of the stated restriction; e.g., “Do not exceed 230 KIAS until passing BRAVO (ATC).” This will indicate to the pilot and the controller that this restriction is for ATC purposes and can be deleted by ATC. The absence of “(ATC)” at the end of a speed restriction indicates that it is there to support a TERPS criteria design constraint and CANNOT be modified or deleted by ATC. (4) ODPs that are depicted graphically must have the term “(OBSTACLE)” printed on the graphic (see appendix D or E). This will be indicated by the word “OBSTACLE” adjacent to the “Type” line on Form 8260-15B, Graphic Departure Procedure. U.S. Government charts will include this immediately following the procedure title; e.g., TETON ONE DEPARTURE (OBSTACLE). (5) ODPs developed for RNAV use must have the terms (OBSTACLE) and (RNAV) printed on the graphic. This will be indicated by the words “OBSTACLE” and “RNAV” adjacent

12/31/12 8260.46D CHG 3

to the “Type” line on Form 8260-15B. U.S. Government charts will include this immediately following the procedure title; e.g., LASCH ONE DEPARTURE (OBSTACLE) (RNAV). (6) All Graphic DPs must include applicable takeoff minimums, climb gradients, obstacle data (see table 2-1), on the graphic chart, even if redundant to information published textually. (7) A Radar Vector Area (RVA) used in conjunction with an RNAV SID may be published on the same chart with an RNAV route departure from a different runway; however, both must contain the same common segment prior to reaching the end of the departure (see appendix E, section 2 for unique database coding requirements). f. Equipment Requirements. DPs are also categorized by equipment requirements as follows: (1) Non-RNAV DP. A DP established for aircraft equipped with conventional avionics using ground-based NAVAIDs; e.g., nondirectional beacon (NDB), very high frequency omni-directional range (VOR), very high frequency omni-directional range/tactical air navigation (VORTAC), localizer (LOC), etc. These DPs may also be designed using dead reckoning navigation. (2) RNAV DP. A DP established for aircraft equipped with RNAV avionics; e.g., global positioning system (GPS), flight management system (FMS), etc. Automated vertical navigation must not be required. (3) Radar SID. A SID established when ATC has a need to vector aircraft on departure to a particular ATS Route, NAVAID, or fix. Radar vectors may also be used to join conventional or RNAV navigation SIDs. SIDs requiring radar vectors must be annotated “RADAR REQUIRED.” g. Terminology. The following terminology applies for initial climb instructions:

(1) When required, departure instructions must specify the actual heading to be flown after takeoff. Example: “Climb heading 350.10....” Some existing procedures specify “Climb runway heading.” Over time, these procedures will be updated, changing the terminology to specify the actual heading being flown. Note: For database coding, heading/track/course values must be in hundredths of a degree. For charting purposes, these heading/track/course values will be rounded to the nearest whole degree. Additionally, hundredths of a degree must not be used in ATC communications. (2) If departure instructions require a heading to be assigned by ATC, use: “Climb on assigned heading for radar vectors to (name of fix/airway, etc.).”

12/31/12 8260.46D CHG 3

(3) If departure instructions require a specific altitude to climb to after takeoff, do not use the terminology “Climb to (altitude) …” without including a heading to fly. Example: “Climb heading 310.25 to 1500 …” (4) Do not use the terminology “Climb straight ahead…” or “Maintain runway track...,” as there is no guidance or reference definition of this phraseology for the pilot to apply. (5) Ensure initial departure instructions that require altitude restrictions are written clearly and in order to be flown so as to lessen the possibility of pilot deviations. For example, “Climb heading 240.15 to 1500, cross TEB 4.5 DME at 1500, then climb and maintain 2000, thence…” or, “Climb heading 195.47 to 900, then climbing right turn heading 280 to maintain 2000, thence…” (6) A departure procedure requiring a turn does not require an initial climb heading to be specified. For example, “Climbing right turn direct XYZ VOR…” Direction of turn must be specified when turn exceeds 15 degrees.

(7) Do not use the word “immediate/immediately” in any type of departure instructions; e.g., turning instruction or speed restrictions. Old “early turn” departure procedures may contain instructions to “Turn left (right) as soon as practicable. This terminology is only to be used on non-standard departure procedures approved by Flight Standards or the appropriate military authority. h. Diverse Vector Area (DVA). An ATC facility may request a DVA be developed to permit vectoring of aircraft on departure, below the Minimum Vectoring Altitude (MVA) or Minimum IFR Altitude (MIA) under the provisions in Order JO 7210.3, paragraph 3-9-5, Establishing Diverse Vector Areas. Order 8260.56, Diverse Vector Area (DVA) Evaluation, until incorporated into Order 8260.3, contains the criteria to be used for development. See appendix G of this order for documenting the development of a DVA. 2-2. Responsibilities. a. General. The following guidance outlines procedures for DP requests, processing, and cancellation. (1) Procedure Requests.

SIDs are normally requested by the ATC facility responsible for departure control at the airport where the procedure is proposed, or by another proponent. All requests for new or amended SIDs must be processed through the Service Area Operations Support Group, Flight Procedures Team (OSG-FPT) and will forward to the appropriate Regional Airspace and Procedures Team (RAPT) in accordance with Order 8260.43, Flight Procedures Management Program. (2) Requirements. ATC must provide the OSG-FPT, detailed operational requirements and restrictions for inclusion in the SID design. AeroNav Products must make every effort to meet ATC identified operational requirements and constraints using current criteria and policy. When current criteria and policy will not support a design to meet ATC

12/31/12 8260.46D CHG 3

requirements, AeroNav Products, Flight Procedure Standards Branch (AFS-420), and other ATO organizations/involved parties must work together to find an acceptable solution. (3) Cancellation. All proposed SID cancellations must be approved by the RAPT. AeroNav Products has sole responsibility for canceling ODPs. AeroNav Products cancels a DVA by notifying the ATC Facility Manager and Support Specialist by phone/E-mail, followed by a memorandum to indicate the previously approved Form 8260-15D, Diverse Vector Area, is no longer valid. b. Proponent. A proponent’s request to develop a DP must include the information in appendices B and C. This information must be completed and forwarded to the ATC facility providing departure control service to the airport for acceptance, prior to development. The DP request package must include the following: (1) An outline of the type of procedure and expected benefits. (2) A proposed ground track, including associated fixes and any proposed altitude or speed restrictions.

(3) A request (if required) for development assistance from the servicing ATC facility. c. ATC. When assisting a proponent or requesting a SID, the ATC facility providing departure control service must: (1) Evaluate the proponent’s request to ascertain preliminary operational feasibility and to determine/verify that significant benefits (see appendix B) will be derived. (2) Assist in designing the procedure by providing the proponent with information pertaining to traffic flow and operational constraints; e.g., routes, minimum IFR altitudes, facility/sector lateral and vertical airspace boundaries, special use airspace, etc. Note: When an ATC facility proposes SID development from an airport served primarily by air carriers, it may attempt to solicit the assistance of a “lead carrier” in the design and flyability of the proposed procedure. (3) Coordinate with other ATC facilities affected by the procedure. (4) Act as the focal point for all ATC coordination and provide appropriate assistance in resolving any problems identified during the development process.

(5) Ensure that a DME/DME screening model has been run on RNAV SIDs to determine if the procedure is useable by suitably equipped aircraft, prior to submission. Note: The DME/DME assessment process is contained in Order 7470.1, DME/DME Infrastructure Evaluation for Area Navigation (RNAV) Routes and Procedures.

12/31/12 8260.46D CHG 3

(6) Coordinate with the servicing ARTCC to obtain a 5-letter pronounceable name for all fixes in the graphic DP. Complete Form 8260-2 data worksheet for each fix being established, modified, or canceled (see appendix C). Include the worksheet(s) as part of the graphic DP request package. Existing fixes/NAVAIDs should be used where conveniently located. (7) Coordinate with the servicing ARTCC to obtain a name and computer code for the SID as specified in appendix A. (8) Complete the DP requirements data worksheet (see appendix B), when applicable. (9) Forward the requested package to the applicable Service Area Operations Support Group. The package must contain worksheets for all fixes, the DP requirements data worksheet, and a sketch of procedures requiring graphic publication (see appendix D or E). (10) Review SIDs at least biennially for continued need. Coordinate requested changes through the applicable Service Area Operations Support Group, Flight Procedures Team.

(11) Collaborate with Performance Based Flight Systems Branch (AFS-470) when the development of an Attention All Users Page (AAUP) is necessary for RNAV departure procedures. See appendix E, section 3, for instructions on filling out Form 8260-15E. d. The Service Area Operations Support Group, Flight Procedures Team must: (1) Review the DP package for completeness. (2) Review DPs for impact based on Facilities and Equipment changes, National Change Proposal (NCP), or other applicable projects. Note: The point-of-contact (POC) and telephone number for the ATC facility is listed on the Graphic DP requirements worksheet. The FPT must contact the POC to resolve any problems in developing the requested procedure and provide appropriate alternatives. The POC must be responsible for additional coordination of changes required for development. The FPT should coordinate with the Regional NextGen Branch (RNGB) for assistance where necessary. (3) Facilitate discussion of the procedure at the RAPT. (4) Forward the DP package to AeroNav Products.

(5) Provide one copy of each 8260-2 and 8260-15 series form(s) to all affected ATC facilities. (6) The OSG-FPT will notify the requesting ATC facility of the anticipated publication date and any delay in the publication and cause.

12/31/12 8260.46D CHG 3

e. AeroNav Products must: (1) Develop and process textual ODPs on Form 8260-15A, Takeoff Minimums and Obstacle Departure Procedures, under applicable directives. (2) Develop and process graphic ODPs and SIDs on Form 8260-15B, Graphic Departure Procedure. (3) Develop and process a Form 8260-15C, Departure Data Record, for all RNAV DPs. (4) Develop and process a Form 8260-15D, Diverse Vector Area, for all DVAs. (5) Ensure that a DME/DME screening model has been run on RNAV “obstacle” departures (the Service Area OSG is responsible for DME/DME screening of SIDs) to determine if the procedure is useable by suitably equipped aircraft, prior to submission for flight inspection. Note: The DME/DME assessment process is contained in separate guidance. (6) Submit DPs to Flight Inspection Operations Division, AJW-391, for necessary action. (7) Ensure that textual ODPs submitted “concurrent” with a “proposed” SIAP are flight inspected prior to assigning an effective date for the SIAP via .26 messages.

(8) After satisfactory flight inspection, forward the original Form(s) 8260-2, Radio Fix and Holding Data Record, and original 8260-15 series forms to NFDC. Copies will be provided to Service Area Flight Procedures Team for distribution to all affected ATC facilities [see paragraph 2-2d(5)]. (9) Develop, review, track, and cancel NOTAMs relating to ODPs and SIDs. (10) Review ODPs periodically for continued need, obstacle clearance, and compliance with current criteria and policy; and coordinate proposed changes with the appropriate ATC facility. When application of new criteria or a new obstacle affects an ODP/SID that requires adjustment to an obstacle-driven CG, all DPs must be evaluated to determine if other CGs require adjustment. If CG adjustments are required, they must be updated simultaneously in the same charting cycle. (11) When a location currently has standard takeoff minimums and circumstances now require non-standard takeoff minimums and/or an ODP development, amend the current Form 8260-15A for the airport accordingly. (12) When it is necessary to cancel a DP, process the appropriate Form 8260-15 as directed in paragraph 2-5d.

12/31/12 8260.46D CHG 3

(13) Add the “T” symbol to the instrument approach procedure (IAP) and SID charts whenever the Form 8260-15A indicates any data entries other than Standard Takeoff Minimums. Note: The “T” symbol will not be placed on graphic ODPs. (14) Delete the “T” symbol from the IAP charts based on receipt of a Form 8260-15A that has “Standard” in the “Takeoff Minimums” and it applies to all runways. This symbol deletion applies when a Textual ODP is not published or when removal of textual ODP information is necessary based on a revised Form 8260-15A. Note: The basic rule is that if an ODP is published (Text or Graphic), the “T” symbol is required on all approach charts to that airport. If an ODP is not published, a “T” symbol will not appear on approach charts. (15) Issue P-NOTAMs to correct United States Government charting discrepancies and compilation errors required (see Order 8260.19, chapter 2, section 6). f.

Flight Inspection Services must: (1) Coordinate and execute Flight Validation and Flight Inspection for FAA developed procedures and under a reimbursable agreement with other instrument flight procedure (IFP) providers, (2) Provide flight inspection results and archived reports upon request, and (3) Verify DME/DME coverage when applicable. g. The NFDC must: (1) Conduct a pre-publication review of submitted forms to ensure compatibility with the National Airspace System Resources, National Database, and compliance with applicable directives relative to form entries. (2) Assign an effective date and publish textual and graphic ODPs in the transmittal letter (TL) authorizing charting agencies to publish the procedure. (3) Assign an effective date and publish graphic DPs, and associated fixes, in the daily National Flight Data Digest (NFDD) authorizing charting agencies to publish the procedure. (4) Coordinate to ensure the Form 8260-15B supporting graphic ODPs is published in the NFDD to be effective and charted concurrently with the associated Form 8260-15A.

(5) Monitor and track the status of concurrent instrument approach procedure (IAP) packages to ensure that the entire package is published with the same effective date.

12/31/12 8260.46D CHG 3

(6) Notify AeroNav Products of delays in publication if the associated proposed procedures have not been flight checked or the associated docket has not received a final date by the applicable cutoff. (7) Resolve data conflicts, form discrepancies, etc., with AeroNav Products. (8) Review and track FDC NOTAMs relating to textual ODPs. (9) File and maintain the original signed copy of the forms. (10) Assign an effective date and publish Form 8260-15E (AAUP) pages supporting RNAV Departures in the NFDD (see paragraph 2-2c(11) and appendix E, section 3). 2-3. Accuracy Verification and Responsibilities. Any ATC facility, DoD, proponent, charting agency, procedure user, concerned individual, organization, or office must: a. Notify AeroNav Products of published errors (including omissions) that affect safety of flight by the fastest means available. AeroNav Products must take appropriate NOTAM action under Order 8260.19. b. Notify the NFDC whenever pre-publication errors are discovered in the TL or NFDD.

The NFDC will coordinate corrective actions with AeroNav Products and promulgate corrected data/forms. c. Notify AeroNav Products whenever charting discrepancies/compilation errors are detected in United States government published aeronautical products. AeroNav Products will coordinate corrective actions with AeroNav Products and NFDC. 2-4. Military Departure Procedures. a. Military DPs are not handled or published in the same manner as civil DPs. Approval authority for DPs at military airports rests with the military. The FAA develops United States Army DPs under Order 8260.15, United States Army Terminal Instrument Procedures Service. The FAA develops United States Air Force DPs at domestic civil airports under Order 8260.32, United States Air Force Terminal Instrument Procedures Service. The National Geospatial-Intelligence Agency (NGA) publishes all military DPs. Note: Military DPs must be named and numbered in accordance with the criteria outlined in this order. b.

The FAA requires that all military DPs be coordinated with FAA ATC facilities or regions when such DPs affect the NAS. The Air Traffic Facility providing the departure service must assist the military in coordinating the procedures and in obtaining computer codes to ensure that the procedures are properly interfaced with the NAS. United States Air Force and Navy procedures are NOT sent to NFDC.

12/31/12 8260.46D CHG 3

c. When military DPs affect airspace under the jurisdiction of FAA facilities, those affected ATC facilities/ARTCCs must maintain copies of the applicable military or FAA procedure approval forms. d. When a military DP has a climb gradient established to clear obstruction(s) that uses the “DoD Option” provision (see Order 8260.3, Volume 4, paragraph 1-4), the procedure must be annotated “NOT FOR CIVIL USE. 2-5. FAA 8260-15 Series Forms (see appendices D through G). a. The 8260-15 series forms document standard takeoff minimums and facilitate transmittal of nonstandard takeoff minimums and/or departure procedures. These forms will be the basis for charting agencies to publish non-standard takeoff minimums, departure procedures, and/or to add/delete charting icons used to denote that other than standard takeoff minimums and/or specific obstacle departure procedures are published.

(1) Use Form 8260-15A. (a) To document standard takeoff minimums. (b) To document nonstandard takeoff minimums and/or higher than standard climb gradients for a runway. (c) To document textual ODPs. (d) To document that the ODP for a runway is published graphically. (e) To document other pertinent textual data for publication; e.g., obstacle data notes, VCOA data, etc. (2) Use Form 8260-15B. (a) To document graphically depicted complex ODPs and all SIDs. (b) To document other pertinent procedural data; e.g., fixes, NAVAIDs, routes, vectoring areas, altitudes, etc. required for charting database development on RNAV DPs. (3) Use Form 8260-15C to document RNAV DPs in a manner consistent with and which aids in charting and database coding. Specifically use 8260-15C to document: (a) The RNAV route of flight in terms of a series of segments defined by fix name, positions, waypoint type, leg types, course, and distance. (b) Altitude and airspeed restrictions associated with fixes.

12/31/12 8260.46D CHG 3

(4) Use Form 8260-15D to document a Diverse Vector Area (DVA). (5) Use Form 8260-15E to document RNAV Departure Procedure Attention All Users Page (AAUP) for locations where it has been determined that detailed departure information is necessary. b. Use Form 8260-15A/B to deny lower than standard takeoff minimums. When touchdown and rollout runway visual range (RVR) are available on runways with centerline lights and either RVR is installed on a baseline GREATER than 250 ft, deny takeoff minimums lower than RVR 1200 by adding the following example standard NOTE on Form 8260-15: “RWY 27R, Air Carrier reduction below RVR 1200 NA.” c. Administratively process the 8260-15 series forms as specified in Order 8260.19, chapter 8. Additionally, when submitting procedures for waiver and/or Flight Standard approvals, include supporting documentation; e.g., for excessive climb gradient approval, submit documentation showing calculations. d. Cancellation of Form 8260-15(s).

Cancel specific takeoff minimums for an airport or cancel any textual or graphical DP(s) no longer required, as follows: (1) Enter the current information from the top line of page 1 of Form 8260-15A/B and into the corresponding blocks on blank Forms 8260-15A and/or B. Additionally, on Form 8260-15B; complete the “Airports Served” section. (2) Enter/Overprint “Canceled effective ” in the “Takeoff Minimums” section on Form 8260-15A and/or “DP Route Description” section of Form 8260-15B (a stamp may be used for this purpose). This effective date will “normally” be entered by NFDC. The only time the “canceled effective” date must be entered by AeroNav Products is when a specific effective date is required. 2-6. Procedure Amendments. All departure procedures may be amended using either the full amendment or an abbreviated amendment process as specified below. A full amendment must ensure that periodic review requirements have been met for the procedures documented on the specific form being completed.

A full amendment requires a complete procedure package (i.e., all necessary forms, maps, and supporting documentation) be developed and submitted for processing. An abbreviated amendment only requires submission of the Forms 8260-15A/B (and 8260-15C, if required) for processing (see Note 2, below). All departure procedures, regardless of the amendment process used, are to be submitted to Flight Inspection for a determination of what action they must take, based on what is being amended. Departure procedures not developed and/or not Flight Inspected by the FAA are to be submitted to AFS-460 to determine Flight Validation requirements. Note 1: Flight Inspection (AFS-460 for procedures not developed and/or Flight Inspected by the FAA) may establish unique/specific policy guidelines with individual procedure development authorities, addressing specific situations that do not require submission for Flight Inspection/

12/31/12 8260.46D CHG 3

Validation. This exception (or exceptions) must be specified in either an FAA Directive or Policy Memorandum controlled by the Flight Inspection/Validation authority. AFS-460 must be provided a copy of all policy memorandums between Flight Inspection and procedure developers. Note 2: When the abbreviated amendment process is used, steps must be taken to insure all supporting documentation, e.g., maps, waiver/approval letters, etc, remain on file in the abbreviated amendment procedure package. a. Textual ODPs. (1) When completing a full amendment, advance the amendment number in the “AMDT No.” item of Form 8260-15A; e.g., “AMDT 1,” “AMDT 4.” When the “abbreviated amendment” process is used, an alphabetical suffix is added/advanced whenever the procedure is revised; for example: “ORIG-A,” “AMDT 5C.” The circumstances dictating the need for revision determine whether an amendment or abbreviated amendment may be made or whether the existing procedure must be canceled and an original established. (2) P-NOTAMs may be used and act as an “abbreviated amendment” for Textual ODPs to effect changes immediately and will generate a publication change, creating a letter suffix as noted in the above paragraph (also see Order 8260.19, chapter 2, section 6). b. Graphic ODPs and SIDs.

(1) Whenever the “DP Name” is changed in the Title line of the Form 8260-15B, or the procedure “Type” is changed, the procedure must be canceled and a new procedure developed. (2) Both the full and the abbreviated amendment processes require the number in the procedure title to be increased; e.g., “SHEMP 2” increases to “SHEMP 3.” (See appendix A, paragraph 2f.) (3) A full amendment is required whenever a change is made to the items listed below as specified on Form 8260-15B: (a) DP Route Description (pertains to entire route charted to include leg lengths when applicable). (b) Transition Routes (adding/revising). (c) Airports Served (Only when airports are added). (4) An abbreviated amendment may be used whenever a change is made to the items listed below as specified on Form 8260-15B. A P-NOTAM must not be used to effect an abbreviated amendment for graphic ODPs and SIDs.

12/31/12 8260.46D CHG 3

(a) Transition Routes (only when removing) (b) Procedural Data Notes/Takeoff Minimums. (c) Takeoff Obstacle Notes. (d) Lost Comm Procedures. (e) Additional Flight Data. (f) Airports Served (only when airports are deleted). (g) Communications. (h) Fixes and/or NAVAIDs (only those requested for charting purposes, but are not included in the textual description of the departure or entered in the transition route data). (i) Remarks (that will require a change to what will be charted on the procedure). (j) Altitude changes (RNAV procedures require RNAV-PRO assessment when altitude changes are made). (5) No amendment is required for changes made to the items listed below as specified on Form 8260-15B.

(a) Controlling Obstacle (that does not require a change to what will be charted on the procedure; change must noted in the procedure package historical information and must be retained until a future amendment/abbreviated amendment Form reflects this new controlling obstacle). (b) Remarks (that do not require a change to what will be charted on the procedure).

12/31/12 8260.46D CHG 3 Appendix A

Appendix A. Guidelines for the Design of Graphic

Instrument Departure Procedures (DPs)

1. General. a. Safety is a primary concern and DPs must be designed so that they provide obstacle clearance, least onerous routing (where possible), and can be confidently and consistently flown by all aircraft expected to use the procedure. b. A DP must be relatively simple and easily understood. To avoid chart complexity and human factors concerns, limit the number of airports and/or runways from which a particular DP may be used to only those necessary to support operations. c. A DP should use only the minimum number of fixes, turns, or altitude changes necessary to depict the route. d. A DP should be developed to accommodate as many different types of aircraft as possible. e. A DP should avoid the use of distance measuring equipment (DME) arcs. f. Graphic ODPs must be designed to terminate at a fix/NAVAID located within the IFR en route structure or at an altitude that will allow random IFR flight. g. A SID must provide for a significant user/system benefit. h. A SID must reduce pilot/controller communications and workload. i.

Appendix A. Guidelines for the Design of Graphic

A SID must be designed to terminate at a fix/NAVAID depicted on an IFR en route chart, at an altitude that will allow random IFR flight, or at a position where ATC radar service is provided. j. Avoid Speed Restrictions Whenever Possible (see paragraphs 2-1d(3) and 2-1e(3) for specific guidance). k. Altitude. (1) Limit the number of altitude requirements to the minimum necessary. ATC operational restrictions are not permitted on ODPs. (2) Minimum and maximum “block” altitudes for the same fix/waypoint are permitted. See paragraph 2-1e(1) for specific guidance and charting constraints. (3) Avoid using multiple altitude restrictions at the same fix for different aircraft types or departure runways; e.g., “Turbo-props cross GRAVY at-or-below 5000, Turbo-jets cross

12/31/12 8260.46D CHG 3 Appendix A

GRAVY at-or-above 6000” or “RWY 9: Cross XRRAY at 9000; RWY 27: Cross XRRAY at 11000. (4) Define crossing altitude restrictions as “At,” “At or Above,” “At or Below,” or “Expect. Avoid “At” and “At-or-Below” altitudes whenever possible. Note: “Expect” altitude restrictions will not be coded. (5) Procedure designers must use good judgment and common sense, coupled with operational input where available, to restrict procedural altitudes due to precipitous terrain. l. Climb Gradient (CG). DPs are designed assuming a minimum standard CG of 200 ft/NM (400 ft/NM for helicopters) to ensure required obstacle clearance is achieved. Higher CGs must be published when required for obstruction clearance and crossing altitude requirements (see paragraphs 2-1d(2) and 2-1e(2) for specific guidance). 2. Naming of DPs (see pages A-6 through A-9 for examples). a. Textual ODPs are not named, while all graphic ODPs and SIDs must be named as described in this section. b.

SIDs, designed using radar vectors as the only navigation source to the en route environment, are normally named to correspond with the terminal control facility name. For example, the SID from Tampa International Airport is named the TAMPA THREE; the SID from Greater Cincinnati Airport is named the CINCINNATI EIGHT. If the terminal control facility name is already in use, use a fix, city, airport, or geographical area name in that order. c. SIDs designed using a diverse vector area and radar vectors to a common specified route must be named to correspond to the fix/NAVAID/waypoint where the specified route ends. For example, the SID uses a diverse vector area and radar vectors to a fix/NAVAID/waypoint that begins a specified route to COTEE; the SID is named the COTEE ONE. d. DPs designed using conventional, RNAV, or RNP guidance must be named to correspond with the en route fix/NAVAID name where the DP ends. For example, a conventional DP from Altoona-Blair County Airport that ends at the TATES fix is named the TATES TWO DEPARTURE.

(1) “RNAV 1” is the default designation for RNAV DPs and it must be included adjacent to the procedure title enclosed in parenthesis. If the DP is an RNAV procedure, the “(RNAV 1)” must be included in the name; for example, TATES TWO DEPARTURE (RNAV 1).

(2) If the DP is an RNP procedure, (RNP 1) must be included adjacent to the procedure title enclosed in parenthesis; for example, TATES TWO DEPARTURE (RNP 1). e. If two or more DPs end at the same fix/NAVAID, the second and subsequent procedures must be named for the city, airport, or geographical area in that order. For example, a

12/31/12 8260.46D CHG 3 Appendix A

SID from Greater Cincinnati Airport that ends at the REDSS fix is named the REDSS FOUR DEPARTURE. A SID from Cincinnati-Lunken Airport that also ends at the REDSS fix is called the LUNKEN SEVEN DEPARTURE. f. Number Each Original Graphic DP “ONE. Number subsequent amendments in numerical sequence through NINE and then start over with ONE (See paragraph 2-6b for the amendment process). 3. Transition Naming. DP transition names must always correspond with the fix/NAVAID where the transition ends. For example, the FORT LAUDERDALE SEVEN DEPARTURE termination fix is the Fort Lauderdale VORTAC (FLL) and it has a transition to the ZAPPA intersection; the transition name is ZAPPA. The REDSS FOUR DEPARTURE terminates at the REDSS fix and it has a transition to the Johnstown VORTAC (JST); the transition name is JOHNSTOWN. 4. Computer Identification Codes (see pages B-6 through B-9 for examples). a. Textual ODPs will not receive a computer identification code. b. Graphic ODPs and SIDs.

Computer identification codes are assigned to graphic DPs by using the abbreviated name of the DP; e.g., a NAVAID or airport 3-letter NAVAID or airport identifier, a 4-letter geographical abbreviation, or a 5-letter fix/waypoint name, or other 5-letter code, followed by the current DP number, then a dot, followed by the fix/NAVAID identifier where the DP ends. For example, the CINCINNATI EIGHT DEPARTURE in appendix A, paragraph 2b is coded “CVG8.CVG;” the FORT LAUDERDALE SEVEN DEPARTURE in appendix A, paragraph 3 is coded “FLL7.FLL;” and the “TATES TWO DEPARTURE in appendix A, paragraph 2d is coded “TATES2.TATES. A computer identification code is not required for radar vector SIDs that do not contain a specified or common route published as part of the SID; i.e., a SID based solely on radar vectors to the en route structure. c. SID Transition. SID transition computer codes are assigned by using the SID identifier and number as noted in appendix A, paragraph 4b, followed by a dot, followed by the identifier of the en route fix where the transition ends.

Using the Fort Lauderdale example in appendix A, paragraph 3, the ZAPPA transition is coded “FLL7.ZAPPA. Using the REDSS example in appendix A, paragraph 3, the Johnstown transition is coded “REDSS4.JST. 5. RNAV DPs. The following general criteria and guidelines apply only to DPs designed for exclusive use by certain RNAV equipped aircraft. See the latest edition of Order 8260.58 for specific guidance and criteria. a. Waypoints. Specify all waypoints as either fly-by or fly-over. (1) Use fly-by waypoints whenever possible. (2) Use fly-over waypoints only when operationally necessary or for obstacle clearance.

12/31/12 8260.46D CHG 3 Appendix A

(3) Design procedures using the fewest number of waypoints. b. Leg Types. Table A-1 shows permissible leg types for use with RNAV DPs. See Order 8260.58 for leg type definitions and examples.

Table A-1. Permissible Leg Types.

FROM VIA (leg type) TO

AER VI1 See 1

AER VA2 ALT

AER VA2 ALT

AER VM8 HDG

ALT CF3, DF4 FB/FO

AER CF3, DF4 FB/FO

FB TF5 FB/FO

FO DF4, TF5 FB/FO

IF7 DF4, TF5 FB/FO

FO VM8 HDG

FB RF6 FB 1 VI (Heading-to-intercept) may only be used as the first leg of a departure and must be followed by a CF leg.

2 VA (Heading-to-an-altitude) may only be used as the first leg of a departure and must be followed by a DF leg. The altitude must be an at-or-above altitude; a mandatory (i.e., “at”) altitude must not be used at the first fix.

FO VM8 HDG

3 CF (Course-to-fix) may only be used as the first leg of a departure or as the leg following a departure VI leg.

4 DF (Direct-to-fix) may be used as the first leg of a departure, the leg following a departure VA leg, and for any leg thereafter preceded by a FO WP only.

5 TF (Track-to-fix) is not used as the first leg of a departure. TF is the preferred leg after the first leg of a departure.

6 RF (Constant radius arc) may only be used when necessary because some users do not have RF capability. An RF leg may only be used after a TF, CF, or another RF leg.

7 IF (Initial fix) is used to designate the first fix of a departure transition, i.e., the IF is coincident with the DP termination fix. IF is also used to designate the point at which RNAV begins when used in conjunction with radar vectors. 8 VM (Vector-to-manual termination) legs are only to be used in conjunction with ATC radar vectoring.

12/31/12 8260.46D CHG 3 Appendix A

Note: AER – approach end of runway, ALT – altitude, FB/FO – fly-by fix/fly-over fix.

c. Leg Length. (1) Use the Longest Legs possible. The designer must consider speed and course changes when determining minimum leg length. See Order 8260.58 for specific minima. (2) There is no maximum leg length for straight-line paths. Exception: Do not develop leg lengths in the en route environment exceeding 260 miles to ensure the geodesic path does not exceed the protected airspace for a great circle path. d. Chart Annotation. (1) All (RNAV 1) and “(RNP 1)” DPs will contain a note that describes the equipment sensor limitations. Notes, as appropriate, are as follows: Note 1: DME/DME/IRU or GPS Required. Note 2: GPS Required. (2) A note may be required to address the need for specific DME facilities to be operational. These are referred to as “critical DME facilities.” Example: Note: For Non-GPS Equipped aircraft, ABC, JKL, and XYZ DMEs Must Be Operational. (3) Except as required by paragraph 2-1f(3), all “(RNAV 1)” DPs that are annotated “DME/DME/IRU or GPS REQUIRED” must be annotated with the note: “RADAR REQUIRED FOR NON-GPS EQUIPPED AIRCRAFT.” (4) When an “(RNP 1)” DP contains a radius-to-fix (RF) leg or all transitions require an RF leg, annotate the procedure with the standard note “RF REQUIRED” (see Note 1, below). If the RNP DP does not require an RF leg, but at least one transition requires an RF leg, define affected transitions as “RF REQUIRED” (see Note 2, below). Note 1: RF Required. Note 2: (Name) Transition, RF Required.

12/31/12 8260.46D CHG 3 Appendix A

EXAMPLES:

084° ABC

R-190

FIXAA

AJT

DEF

GHI

JACKSON

JKL

18

27

BASIC SID ENDS AT JKL

JACKSON ONE DEPARTURE (JKL1.JKL)

340°

SID WITH NO TRANSITIONS

R-348

R-261

R-254

R-262 077° 081°

072°

12/31/12 8260.46D CHG 3 Appendix A

EXAMPLES (Continued):

MOEHH

SID WITH NO TRANSITIONS

LARRY

CURLY

#Course/Heading/Track

not shown for DF legs.

SHEMP

SHEMP1.FGH

SHEMP1.JKL

JKL

FGH

SHEMP1.LMN

LMN

SHEMP1.RST

RST

SHEMP ONE DEPARTURE (RNAV) (SHEMP1.SHEMP)

TF

(16.5)

094°

TF

(4.8) 039°

5000 *4100

(47)

155° TF

5000 *3700

(87) 067° TF

DF

#

DF

(20.9)

#

VA 318°

008° CF

(5.8)

SHEMP ONE DEPARTURE (RNAV) (SHEMP1.SHEMP)

CF 138° (2.4)

5000

(93) 099°

7000 *4400

(40) 098°

TF

TF

RNAV SID WITH FOUR TRANSITIONS

1000

1000

12/31/12 8260.46D CHG 3 Appendix A

EXAMPLES (Continued):

MOEHH

LARRY

1000

2000

3000

1000 CURLY

#Course/Heading/Track

not shown for DF legs.

SHEMP

SHEMP2.FGH

FGH SHEMP2.OPQ

OPQ

SHEMP2.JKL

FGH SHEMP2.OPQ

JKL

SHEMP2.RST

RST

SHEMP TWO DEPARTURE (RNAV) (SHEMP2.SHEMP)

TF

(15.0)

092°

TF

(7.5) 039°

5000 *3700

(87) 067°

4000 *3300

(52) 005°

DF or TF

#

DF or TF #

DF

#

VA 318°

CF

(3.1)

138°

5000

(93) 099° DF or TF

#

7000 *4900

(77)

129° DF or TF

#

RNAV SID WITH FOUR TRANSITIONS

8000 5000

RNAV SID WITH FOUR TRANSITIONS

008° CF

(5.8)

TF

(20.7) 060°

BHILY

BHILY3.FGH

BHILY3.JKL

FGH BHILY3.OPQ OPQ

JKL

LMN

BHILY3.RST

RST

BHILY THREE DEPARTURE (BHILY3.BHILY)

5000 *3700

(87) 067°

4000 *3300

(52) 005°

R-337

5000

(93) 099°

47

7000 *4900

(77)

129°

RADAR DEPARTURE WITH 4 TRANSITIONS

12/31/12 8260.46D CHG 3 Appendix A

RADAR DEPARTURE WITH 4 TRANSITIONS

EXAMPLES (Continued):

FLAVR ONE DEPARTURE (RNAV) (FLAVR1.FLAVR)

RNAV DEPARTURE USING RADAR

VECTORS, FOUR TRANSITIONS

FLAVR1.FGH

FLAVR1.JKL

FGH FLAVR1.OPQ OPQ

JKL

FLAVR1.RST

RST

5000 *3700

(85) 065°

4000 *3300

(55) 334°

5000

(89) 098°

7000 *4900

(73)

130°

TF

4000 *3000

(15) 075°

FLAVR

FGH FLAVR1.OPQ OPQ

WAYPT

A-9 (and A-10)

THIS PAGE IS INTENTIONALLY LEFT BLANK

12/31/12 8260.46D CHG 3 Appendix B

Appendix B. Instructions for Completing Graphic Departure Procedure (DP) Requirements Worksheet

Instructions for completing the graphic departure procedure requirements worksheet by other than AeroNav Products personnel. Note: Proponents with the capability may use electronically generated 8260-15 series forms (with graphic depiction included) instead of the Graphic DP Requirements Worksheet. This worksheet may be used to process changes to existing DPs. In such cases, only complete those Lines needed to convey the request/recommendation. 1. Line 1. Airport(s). Enter the name(s) of the airport(s) and the ICAO identifier(s) of each. 2. Line 2. City and State. Self-explanatory. 3. Line 3. DP Name and Computer Codes. Enter the proposed name of the DP and computer code. Use the naming and computer code conventions as outlined in appendix A. Coordinate the proposed name(s) and code(s) with the servicing ARTCC to ensure there are no duplications. 4. Line 4. Action Required. Indicate whether a new procedure is being established or modifying an existing DP. 5. Line 5. Communications.

Appendix B. Instructions for Completing Graphic Departure Procedure (DP) Requirements Worksheet

Indicate the communications functions to be charted; e.g., ATIS, AWOS/ASOS, CTAF, CLNC DEL, DEP CON, etc. List specific frequency(ies) only when multiple frequencies are available at a facility and there may be confusion as to which should be assigned to the procedure, or if the frequency(ies) are unique to the procedure. Coordinate with ATC as necessary. 6. Line 6. Route. a. Line 6.1. Runway(s)/Helipads/Vertiports. Indicate the runway number(s) or helipads/vertiports the DP will serve. b. Line 6.2. Initial Route From Runway. Indicate the desired initial route(s) that is required. If known, specify the single heading/course, or range of headings (e.g., DVA headings) for each runway authorized for the SID. c. Line 6.3. ATC Requested Routing/Operational Parameters. Enter any information that would assist the procedure developer by providing flexibility in ground tracks. For example, if ATC needs the departure track to go generally south and join a route at a specified point and the exact ground track is not important, so state.

Conversely, if there is flexibility to the east but there is an operational constraint to the west, that information must be provided. In extraordinary cases, when exact ground track is the primary concern in RNAV DPs, specify desired routing. ATC should specify the routing based on ATC needs.

04/14/11 8260.46D CHG 1 Appendix B

d. Line 6.4. Fix(es). Enter each fix in the order flown. For the Departure IF, indicate either a specific point or at least describe the factors constraining the placement of the fix. Enter coordinates to the nearest 0.01 arc second when known. The TARGETS distribution package will satisfy this requirement. If used, enter the statement “See attached (DP name) TARGETS distribution package dated (date). Note: If an existing fix/NAVAID is used, enter only the fix name/facility type and ID, and any altitude restriction at the fix. e. Line 6.5. ATC Required Altitudes. Enter any altitude restrictions associated with each fix. 7. Line 7. Transitions. [NA for Obstacle Departure Procedures (ODPs)] a. Line 7.1. Identification. Enter the proposed name and computer code of each transition (see Block 3). b. Line 7.2. Transition Fix(es). See Block 6.4. c. Line 7.3. ATC Required Altitudes. See Block 6.5. d. Line 7.4. ATC Operational Parameters. See Block 6.3. 8. Line 8. Lost Communications. List specific lost communications instructions if other than 14 CFR Part 91.185 (standard). 9. Line 9.

Graphic Depiction. Provide a basic sketch of the procedure. The sketch may be hand drawn, computer generated, or overlaid on the appropriate portion of a controller chart. It is not necessary for the sketch to be to an exact scale. The intent here is to provide the procedure developer with a visual correlation of the textual route description. 10. Line 10. Requested Publication Date or Airspace Docket Number. Enter the desired effective date that coincides with the charting cycle. If the DP effective date is to be concurrent with an airspace action, enter the docket number, which may be obtained from the applicable ATO Service Area. See Order 8260.26, appendix A for chart dates and lead-time for submission. 11. Line 11. Remarks. a. Indicate that the environmental review under Order 1050.1 (latest edition) and the noise screening have been accomplished. Note: Notice 7210.360, Noise Screening Criteria for Certain Air Traffic Actions Above 3000 Feet, has expired; however, the noise screening is still required.

The requirement will be re-established in a proposed Air Traffic environment order.

04/14/11 8260.46D CHG 1 Appendix B

b. Enter appropriate information to clarify a data entry; e.g., airspeed restriction for air traffic, maximum altitude for aircraft performance, etc. c. If the proposed DP does not meet the criteria requirements in chapter 2, paragraph 2-1 of this order, a statement of justification is necessary to explain why a DP is required. Avoid publication of unnecessary DPs. 12. Line 12. Point of Contact (POC). Self-explanatory.

04/15/11 8260.46D CHG 1 Appendix B

THIS PAGE INTENTIONALLY LEFT BLANK

THIS PAGE INTENTIONALLY LEFT BLANK

12/31/12 8260.46D CHG 3 Appendix B

Graphic Departure Procedure (DP)

Requirements Worksheet 1. Airport(s) … … … … … 2. City and State 3. DP Name … Computer Code 4. Action Required: Establish ____ Amend … 5. Communications: Enter an X in the space provided next to the communications function listed. Enter specific frequency(ies) only when multiple frequencies are available at a facility and there may be confusion as to which should be assigned to the procedure, or if the frequency is unique to the procedure.

ATIS AWOS/ASOS CLEARANCE DELIVERY GROUND TOWER CTAF DEPARTURE CONTROL ARTCC 6. Route: 6.1. Runway(s) … Helipads/Vertiports 6.2. Initial Route From Runway 6.3. ATC Requested Routing/Operational Parameters 6.4. Fix(es):

NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT

6.5. ATC Required Altitudes:

04/15/11 8260.46D CHG 1 Appendix B

Graphic Departure Procedure (DP)

Requirements Worksheet (Continued) 7. Transitions: [Not Allowed for graphic Obstacle Departure Procedures (ODPs)] 7.1 Identification:

NAME … COMPUTER CODE …

NAME … COMPUTER CODE …

NAME … COMPUTER CODE …

NAME … COMPUTER CODE …

NAME … COMPUTER CODE … 7.2 Transition Fix(es): Note: If fix/NAVAID is currently published on an en route chart, enter only the fix name and/or facility ID, and required altitude.

NAME … COMPUTER CODE …

NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT NAME NAVAID LAT/LONG … ALT

7.3. ATC Required Altitudes:

7.4. ATC Operational Parameters:

8. Lost Communications:

04/15/11 8260.46D CHG 1 Appendix B

Graphic Departure Procedure (DP)

Requirements Worksheet (Continued)

9. Graphic Depiction: Note: Depiction must clearly portray intended routing, fixes, NAVAIDs, and altitudes to be used in the DP. A separate sheet may be used. 10. Request Publication Date or Airspace Docket Number … 11. Remarks:

12. Point-of-Contact: …

12. Point-of-Contact: …

ATC Facility Name.

POC’s Name.

Telephone Number.

FAX Number.

E-Mail Address.

04/15/11 8260.46D CHG 1 Appendix B

THIS PAGE INTENTIONALLY LEFT BLANK

04/14/11 8260.46D CHG 1 Appendix C

Appendix C. Instructions for Completing

FAA Form 8260-2, Data Worksheet

Instructions for completing 8260-2, Data Worksheet, for Air Traffic facilities requesting AeroNav Products initiation or modification of fixes (including “Fix Use” updates) associated with existing Part 95 routes, Part 97 approaches, SID or STARs. For others (e.g., non-FAA procedure developers, etc.) that will be using existing fixes maintained by AeroNav Products and only need to update the “Fix Use,” complete the form with as much information as possible and explain the addition or deletion in Block 9, Remarks. 1. Line 1. Requested Publication Date. Enter the desired effective date that coincides with the charting cycle (see the latest edition of Order 8260.26, appendix 1). If the Form 8260-2 request is to be in conjunction with an airspace action, obtain the docket number from the applicable ATO Service Area. For Form 8260-2 requests associated with a DP request, allow at least 20 weeks lead-time from the desired effective date. 2. Line 2. Fix Name. Enter the 5-character pronounceable name obtained from ARTCC. Do not include “WP” as part of the name. 3. Line 3. Fix Type.

Appendix C. Instructions for Completing

Indicate the type of fix; e.g., radar, WP (a geographical position), DME (fixes made up of a single radial/bearing and DME, or multiple DMEs), VHF (fixes made up of 2 VOR radials), VHF/LF (fixes made up of a VOR radial and an NDB bearing). Indicate all combinations that make up the fix. 4. Line 4. State. Enter the state in which the fix is located. 5. Line 5. Location. Latitude and longitude accurate to the hundredth of a second; e.g., 09.25 sec. NAVAID radial/bearing/distance values must also be entered to the appropriate hundredth value; e.g., 347.23; 08.37NM. 6. Line 6. Type of Action Required. Check applicable box to Establish, Modify, or Cancel the fix. 7. Line 7. Holding. List holding patterns required at fix. Include minimum and maximum altitude required. Include speed if other than standard. 8. Line 8. Charting. Indicate required charting; i.e., terminal, en route, SID, STAR, etc. 9. Line 9. Remarks. Other airports/procedures associated with fix (if known). Justify the requirement for other than routine processing and charting.

Include any other information that may assist in developing the fix. 10. Line 10. Point of Contact (POC). Self-explanatory.

THIS PAGE INTENTIONALLY LEFT BLANK

08/20/09 8260.46D Appendix C

Form 8260-2, Data Worksheet 1. Requested Publication Date: 2. Fix Name: 3. Fix Type: 4. State: 5. Location: 6. Type of Action Required: Establish Modify Cancel 7. Holding: 8. Charting: 9. Remarks (Use additional paper if required): 10. Point of Contact (POC):

THIS PAGE INTENTIONALLY LEFT BLANK

ATC Facility Name. POC’s Name. Telephone Number. FAX Number. E-Mail Address.

THIS PAGE INTENTIONALLY LEFT BLANK

12/31/12 8260.46D CHG 3 Appendix D

Appendix D. Section 1. Instructions for Completing

FAA Form 8260-15A, Takeoff Minimums and Obstacle Departure Procedures (ODP) and Sample Forms 1. Develop a separate Form 8260-15A for each airport with approved instrument procedures. If all runways are standard (e.g., no ODP required), then state “Standard. The form must encompass all runways for that airport. Use table A-1 as a guide to initiate the required “Action” to support the “Situation” for a specific airport. 2. City and State. Complete this section with the same location data as on the associated approach procedure(s). 3. Airport. Complete this section with the same airport name data as on the associated approach procedure(s). 4. Effective Date. Leave blank. The National Flight Data Center (NFDC) will normally add the effective date. Enter an effective date only when a specific effective date is required; e.g., Magnetic Variation (Mag Var) rotation. If the procedure is a “Special,” the effective date will be entered by the Regional Flight Standards Division, NextGen Branch (RNGB). 5. AMDT No. Enter standard entry as on Standard Instrument Approach Procedures (SIAP). 6.

Appendix D. Section 1. Instructions for Completing

Takeoff Minimums. Enter takeoff minimums as directed below; however, do not list Takeoff Minimums for the runway(s) served by a graphic ODP - see appendix D, paragraph 7a(6). a. List the runway(s) that are not authorized for IFR departures. If none of the actions listed in table A-1 are feasible, or if another reason(s) precludes ODP development (noise abatement, environmental, etc.), an IFR departure must not be authorized. Examples: RWY 27, NA - OBSTACLES. RWY 35, NA - ENVIRONMENTAL. RWY 17, NA - OBSTACLES AND NOISE ABATEMENT. Followed by: b. List the runway(s) authorized standard takeoff minimums. Example: RWY 09, 31 STANDARD. Followed by:

12/31/12 8260.46D CHG 3 Appendix D c. List the runway(s) that have any deviations from standard minimums and/or restrictions; Example: TAKEOFF MINIMUMS: RWY 13, 400-2 OR STANDARD WITH MINIMUM CLIMB OF 310 FT/NM TO 900, OR ALTERNATIVELY, WITH STANDARD TAKEOFF MINIMUMS AND A NORMAL 200 FT/NM CLIMB GRADIENT, TAKEOFF MUST OCCUR NO LATER THAN 1800 FT PRIOR TO DER. (1) When obstacles in the initial climb area (ICA) cause a climb gradient to an altitude 200 ft or less above DER, before rounding, do not publish takeoff minimums or a climb gradient. Instead, identify the obstacle data by note for publication in the “Takeoff Obstacle Notes” section.

(2) When obstacles 3 SM or less from DER preclude standard takeoff minimums: Note: The obstacle may be within the ICA or ICA extended to 3 SM. (a) Provide a Note identifying the obstacle(s) in the “Takeoff Obstacle Notes” section. (b) Provide higher than standard takeoff minimums followed by the alternative of standard minimums with a specified climb gradient. (c) Identify the obstacle(s) on which the published ceiling and visibility is based in the Controlling Obstacles section. (3) When obstacles beyond 3 SM of DER preclude standard takeoff minimums: (a) Provide standard takeoff minimums with minimum climb gradient requirements. (b) Provide higher than standard takeoff minimums to allow a visual climb over the airport (VCOA). Use standard Note in the following format: RWY XX, (CIG/VSBY) for VCOA. Example: TAKEOFF MINIMUMS: RWY 9, STANDARD WITH MINIMUM CLIMB OF 310 FT/NM TO 1400 OR ALTERNATIVELY, WITH STANDARD TAKEOFF MINIMUMS AND A NORMAL 200 FT/NM CLIMB GRADIENT, TAKEOFF MUST OCCUR NO LATER THAN 1800 FT PRIOR TO DER OR 1100-2½ FOR VCOA. 7. TEXTUAL Departure Procedure.

12/31/12 8260.46D CHG 3 Appendix D a. When a specific departure route is necessary, provide the complete text, by runway, for required DPs. (1) When a climb to an altitude is necessary before turning, define the limitation as clear and simple as possible when limiting the initiation of a turn; e.g., “RWY 36 – CLIMB HEADING 350.11 TO 2800 BEFORE TURNING LEFT. Note: Procedure designers must consider the impact on local ATC operations when using such phrases as “before turning” or “before proceeding on course;” therefore, coordinate these actions with ATC to ensure compatibility with the local operating environment. (2) When a DP routing is required and VOR or TACAN is used to define the route, use the format: RWY 9 - CLIMBING LEFT TURN TO INTERCEPT ABC VORTAC R-310 TO 6000 BEFORE PROCEEDING ON COURSE.

(3) When a DP routing is required and NDB is used to define the route, use course to or bearing from the NDB; e.g., RWY 35 - CLIMB HEADING 350…, THEN CLIMBING RIGHT TURN TO INTERCEPT BEARING 020 FROM ABC NDB TO 6000 BEFORE PROCEEDING ON COURSE; or RWY 35 - CLIMB HEADING 030…, THEN ON COURSE 015 TO ABC NDB TO 4000 BEFORE PROCEEDING ON COURSE. (4) When a ODP routing permits a climb within a sector, define the courses to remain within in a clockwise fashion; e.g., “RWY 12 – CLIMB ON A HEADING BETWEEN 061 CW TO 228 FROM DEPARTURE END OF RUNWAY, OR MINIMUM CLIMB OF 260 FT PER NM TO 8700 FOR HEADINGS 229 THROUGH 300. (5) When a DP routing is required and a localizer course is used to define the route, use magnetic direction of localizer course to be flown; e.g., “RWY 5 - CLIMB ON I-XXX LOCALIZER NE COURSE TO 3000 BEFORE TURNING.

(6) When the departure instructions must be graphically depicted, inform the pilot of the name of the default Obstacle DP, and submit an accompanying Form 8260-15B; e.g., Use standard Note: “USE JONES DEPARTURE” when the graphic obstacle DP serves all runways or use “RWY 27 – USE SMITH DEPARTURE” when the graphic obstacle DP serves only a specific runway. b. It is not appropriate to use the wording “Comply with ODP or.... This could be confusing and cause the pilot to use a different routing than was expected by ATC. c. Do not use the phrase “...or comply with ATC instructions. The pilot is aware that ATC instructions are to be complied with, when possible, and safety of flight is not compromised.

12/31/12 8260.46D CHG 3 Appendix D d. Specify a single obstacle DP. Do not provide an option to use a SID as the default ODP. For example, do not use “Climb runway heading to 1200 before turning or use Manchester Departure. 8. Visual Climb Over Airport. a. When a VCOA has been established, include instructions to climb in visual conditions to cross a specified airport, NAVAID or fix at or above a specified altitude before proceeding on course. b. The statement “Obtain ATC approval for VCOA when requesting IFR clearance” must be included at the beginning of the VCOA instructions. Examples: RWY 19 – OBTAIN ATC APPROVAL FOR VCOA WHEN REQUESTING IFR CLEARANCE. CLIMB IN VISUAL CONDITIONS TO CROSS HICKORY REGIONAL AIRPORT AT OR ABOVE 1200 BEFORE PROCEEDING ON COURSE. ALL RUNWAYS – OBTAIN ATC APPROVAL FOR VCOA WHEN REQUESTING IFR CLEARANCE. CLIMB IN VISUAL CONDITIONS TO CROSS XYZ VOR SOUTHEAST BOUND AT OR ABOVE 4200 THEN PROCEED ON XYZ R-150 TO HAMET. 9. Takeoff Obstacle Notes. a.

Enter a Note regarding obstacles found as a result of applying table A-1, Situation 2 action and Situation 3, action “A.” See appendix D, paragraph 6c(2). Do not list Takeoff Obstacle Notes for the runway(s) served by a graphic default Obstacle DP as described in appendix D, paragraph 7a(5). Note: An adverse assumption obstacle (AAO) will not be identified/published as a “takeoff obstacle” because pilots are not familiar with the AAO concept. However, publishing a ceiling and visibility will allow for those situations where the CG cannot be achieved and still afford the pilot the opportunity to visually acquire and avoid any obstruction that could have been built without notice to the FAA. b. The note must include the runway affected and inform the pilot of the obstacle(s) type and location relative to the DER and height (AGL/elevation (MSL). When there are obstacles on both sides of the runway centerline extended, note the most significant obstacles left and right of the runway centerline. Phrases such as “multiple antennas, numerous trees, etc.” are acceptable.

Specify distances 1 NM or greater to the nearest whole and tenth of a NM (e.g., 2.1 NM FROM DER). Specify distances less than 1 NM in feet (e.g., 1280 FT FROM DER).

12/31/12 8260.46D CHG 3 Appendix D Examples: NOTE: RWY 35, TREES 1280 FT FROM DER, 120 FT LEFT OF CENTERLINE, 50 FT AGL/1527 FT MSL. NOTE: RWY 35, BUILDING 2.1 NM FROM DER, 160 FT LEFT OF CENTERLINE, 350 FT AGL/1927 FT MSL. NOTE: RWY 17, MULTIPLE BUILDINGS 500 FT FROM DER, 350 FT RIGHT OF CENTERLINE, 50 FT AGL/1107 FT MSL. ANTENNA 6000 FT FROM DER, 1235 FT LEFT OF CENTERLINE, 200 FT AGL/1257 FT MSL. NOTE: RWY 27, MULTIPLE TREES AND ANTENNAS BEGINNING 500 FT FROM DER, 350 FT RIGHT OF CENTERLINE, UP TO 110 FT AGL/1307 FT MSL. c. These obstacle Notes must be published by charting agents. 10. Controlling Obstacles. a. Document the controlling obstacle(s) found as a result of applying table 2-1, Situation 3 and/or Situation 4. See appendix D, paragraph 6c(2). When there is more than one controlling obstacle to be documented, following the coordinates, include what entity it applies too; i.e., “(Ceiling),” “(Visibility),” “(Climb Gradient),” or “(Climb-To Altitude).” Do not list Controlling Obstacles for the runway(s) served by a graphic default ODP as described in appendix D, paragraph 7a(5).

Note: For all DPs, the controlling obstacle is that obstacle which, having penetrated the 40:1 Obstacle Clearance Surface (OCS) causes the most adverse climb gradient, climb-to altitude, and/or ceiling and visibility to be published. b. Use the following format to list the runway affected, elevation, and type of obstacle, the coordinates to the nearest 0.01 second; e.g., “RWY 32: 2049 FT MSL ANTENNA 341548.01N/ 0862101.05W” or “RWY 32: 2049 FT MSL ANTENNA 341548.01N/ 0862101.05W.” c. Document the obstacle(s) that mandated development of a specific textual ODP route. These obstacles are not considered the “controlling obstacles” because they are not a factor to the specified route being flown. This information will not be charted on the procedure. Document these obstacles as follows: “OBSTACLES MANDATING ODP ROUTE DEVELOPMENT: RWY 36 - 2049 FT MSL ANTENNA 341658.01N/ 0863108.05W.” 11. Remarks. List information/data that is not normally charted; e.g., administrative data or notes for controller information (requested by ATC). However, if something does need to be charted, precede the text with the “Chart Note:” annotation. See Order 8260.19, paragraph 8-72g,

12/31/12 8260.46D CHG 3 Appendix D for a chart note that is required if the ODP is a Special. General chart notes (not Takeoff Minimums or Departure Instructions Notes) need to include instructions to the chart organization to place the note at the bottom of the entry. Use the following format: “Chart Note at bottom of entry:…” 12. Flight Inspected By. Enter the name of the pilot who conducted the flight inspection/validation, and the date. 13. Developed By. Enter the name of the FAA procedure specialist and organizational routing code. If developed under an Other Transactional Authority, enter the procedure developer's name and organization. 14. Approved By. Enter the name of AeroNav Products Manager, or his/her delegated representative. For procedures developed under an Other Transactional Authority, enter the name of the organization's manager or his/her delegated representative. This individual must sign in the “approved by” space, and enter the date signed. If the procedure is a “Special,” this line will contain the name of and be signed by the manager, AFS-400. 15.

Coordinated With. Specify the offices/organizations the procedure was coordinated with. DP coordination must be identical with the approach procedure coordination as outlined in Order 8260.19, Flight Procedures and Airspace, (latest edition), chapter 8. 16. Changes. List changes relating to data entries on page one. 17. Reasons. List reasons for changes relating to data entries on page one. Additionally, when a VCOA cannot be established, an explanation must be provided; e.g., “VCOA NOT ESTABLISHED AT ATC REQUEST DUE TO (REASON). 18. Required Effective Date. a. Enter the effective date as noted in Order 8260.19 (latest edition), chapter 8, except that “Proposed” dates may not be used for ODPs. Optimally, submit as routine. Note: En route submission cutoff dates apply to graphic DPs. b. If the Form 8260-15A represents a concurrent action, enter “CONCURRENT” followed by the necessary information; e.g., Airport ID, IAP name and amendment number; airspace action, or other event. c.

When documenting Standard Takeoff Minimums where all runways have a clear 40:1 Obstacle Clearance Surface (i.e., No ODP or obstacle notes required), enter “N/A.”

12/31/12 8260.46D CHG 3 Appendix D

Figure D-1.

12/31/12 8260.46D CHG 3 Appendix D

THIS PAGE IS INTENTIONALLY LEFT BLANK

Continue reading ↓ 120 of 228 passages shown