Radar Vectors
FAA Order Cancelled Issued May 30, 2014 AFS-400 146 pages Copy saved Nov 18, 2026

Order 8260.46E Departure Procedure (DP) Program

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

Official source ↗ Open PDF

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

This order provides the policy, guidance, and standardization for initiating, developing, processing, and managing the Departure Procedure (DP) Program. The original order combined into a single product textual instrument flight rules (IFR) departure procedures and graphical Standard Instrument Departures (SIDs). It made no distinction between area navigation (RNAV) DPs: those developed solely for obstruction clearance and those developed for system enhancement. This document defines two separate types of DPs: SIDs developed for system enhancement and Obstacle Departure Procedure (ODPs) developed solely for obstruction clearance.

John S. Duncan Director, Flight Standards Service

Effective Date:

05/30/2014

National Policy

SUBJ: Departure Procedure (DP) Program

ORDER 8260.46E

Distribution: Electronic Distribution Initiated By: AFS-400

05/30/2014 8260.46E Table of Contents

Table of Contents

Chapter 1. General Information … 5

Section 1-1. Basic … 5

1-1-1. Purpose of this order … 5 1-1-2. Audience … 5 1-1-3. Where you can find this order … 5 1-1-4. What this order cancels … 5 1-1-5. Effective Date … 5 1-1-6. Explanation of Changes … 5

Chapter 2. Responsibilities … 11

Section 2-1 … 11

2-1-1. Departure Procedure (DP) Guidelines … 11 2-1-2. Responsibilities … 26 2-1-3. Accuracy Verification and Responsibilities … 31 2-1-4. Military Departure Procedures (DPs) … 31 2-1-5. FAA 8260-15 Series Forms (see appendices D through G) … 32 2-1-6. Procedure Amendments … 33

Chapter 3. Guidelines for the Design of Graphic Instrument Departure Procedures (DPs) … 37

Section 3-1 … 37

3-1-1. General … 37 3-1-2. Naming of DPs (see examples at the end of this chapter) … 38 3-1-3. Transition Naming … 39 3-1-4. Computer Identification Codes … 39 3-1-5. RNAV DPs … 39 3-1-6. Examples of Various Graphic Departure Scenarios … 42

Appendix A. Administrative Information … 47

1. Distribution … 47 2. Background … 47 3. Definitions … 47 4. Related Publications … 50 5. Forms and Reports … 51 6. Information Update … 51

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

Appendix C. Instructions for Completing FAA Form 8260-2, Data Worksheet … 61

Appendix D … 63

05/30/2014 8260.46E Table of Contents

Section 1. Instructions for Completing FAA Form 8260-15A, Takeoff Minimums and Obstacle Departure Procedures (ODP) and Sample Forms … 63

Section 2. Instructions for Completing FAA Form 8260-15B, Graphic Departure Procedure (DP) [Non-RNAV Departure Procedures] and Sample Forms … 79

Appendix E … 91

Section 1. Instructions for Completing FAA Form 8260-15B, Graphic Departure Procedures (DP) [RNAV Departure Procedures] and Sample Forms … 91

Section 2. Instructions for Completing FAA Form 8260-15C, Departure (Data Record) and Sample Forms … 111

Section 3. Instructions for Completing FAA Form 8260-15E, RNAV Departure Procedure Attention All users Page (AAUP) [RNAV Departure Procedure] and Sample Form … 123

Appendix F. Helicopter RNAV Departure Procedures … 129

Appendix G. Instructions for Completing FAA Form 8260-15D … 141

05/30/2014 8260.46E Table of Contents

THIS PAGE IS INTENTIONALLY LEFT BLANK

Chapter 1. General Information

Section 1-1. Basic

1-1-1. Purpose of this order. This order provides policy, guidance, and standardization for initiating, developing, processing, and managing the DP program.

1-1-2. Audience. The primary audience for this order is the Air Traffic Organization (ATO) Mission Support Services (MSS) and all service providers (as defined in appendix A) who have the responsibility to develop instrument departure procedures. The secondary audience includes all other Air Traffic Organizations (ATO), Flight Standards headquarters, and regional office Divisions/Branches who have responsibilities related to instrument departure procedures.

b. Chapter 2. › (3) Paragraph 2-1-1b(7). Revised text for clarity.

1-1-3. Where you can find this order. You can find this order on the Directives Management System (DMS) website 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-1-4. What this order cancels.

a. Order 8260.46D, Departure Procedure (DP) Program, dated August 20, 2009 and all associated changes.

b. AFS-400 memorandum dated April 18, 2013, “Clarification to Order 8260.46D, Departure Procedure (DP) Program – Takeoff Obstacle Notes for Helicopter Departure Procedures.”

c. AFS-400 memorandum dated May 7, 2013, “Clarification to Order 8260.46D, Departure Procedure (DP) Program – Cancellation of FAA 8260-15 Series Form.”

1-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. Use previous editions until implementation has commenced, not to exceed 24 months from the new effective date.

1-1-6. Explanation of Changes.

a. Chapter 1. Added reference to audience refers to appendix A of “service providers.”

b. Chapter 2.

(1) Paragraph 2-1-1b. Added guidance on the application of newly added figures 2-1-1, 2-1-2, and 2-1-3.

(2) Paragraph 2-1-1b(6). Editorial and revised text, replacing “route” with “method” to clarify that the primary emphasis when developing an ODP is to use the least onerous “method” available. A “route” departure is one of those methods.

(3) Paragraph 2-1-1b(7). Revised text for clarity.

b. Chapter 2. › (21) Paragraph 2-1-2d.

(4) Paragraph 2-1-1b(10). Editorial.

(5) Paragraph 2-1-1b(12). Editorial.

(6) Added figures 2-1-1, 2-1-2, and 2-1-3.

(7) Paragraph 2-2-1c(1). Editorial.

(8) Paragraph 2-2-1c(2). Added reference to “course to be flown” to support use of an FM leg type.

(9) Paragraph 2-1-1d(2). Editorial and deleted “whether for obstacle clearance or air traffic control restrictions.”

(10) Paragraph 2-1-1d(2) Note. Editorial.

(11) Paragraph 2-1-1d(3). Editorial and removed references to ATC speed restrictions.

(12) Paragraph 2-1-1d(7). Added guidance to clarify that this limitation applies to both lateral and vertical portions of the departure procedure and it applies to the end of the SID.

(13) Paragraph 2-1-1e(1)(b) Note. Added note to remind procedure developers to consider aircraft performance limitations when establishing fix crossing altitudes to support ATC requests.

(14) Paragraph 2-1-1e(2). Revised “climb gradient” application to provide climb gradients in excess of 200 ft per NM for supporting obstacle clearance and/or RNAV engagement altitude. Added Note information regarding helicopter climb gradients.

(15) Paragraph 2-1-1e(3)(b). Expanded guidance on how to document a speed restriction.

(16) Paragraph 2-1-1e(3)(c). Deleted paragraph.

(17) Paragraph 2-1-1g(1). Editorial.

(18) Paragraph 2-1-1i. Added paragraph to expand guidance regarding publication of Attention All Users Page (AAUP).

(19) Paragraph 2-1-2a(4). Added paragraph at the ATO’s request regarding their Safety Risk Management (SRM) responsibilities.

(20) Paragraph 2-1-2c(11). Changed reference for AAUP guidance.

(21) Paragraph 2-1-2d. At the request of the ATO, moved paragraphs 2-1-2c(4) and (5) (ATC responsibilities) to become the responsibility of the Service Area Operations Support Groups. Also at the request of the ATO, added paragraph requiring Service Area Operations Support Groups to comply with their Safety Risk Management (SRM) requirements.

1-1-6. Explanation of Changes. › c. Chapter 3.

(22) Paragraph 2-1-2e(7). Deleted; “proposed” instrument procedures are no longer permitted under Order 8260.26F. Paragraphs re-numbered accordingly.

(23) Paragraph 2-1-2e(7). Revised to reflect actual processing steps.

(24) Paragraph 2-1-2e(9). New (remaining paragraphs renumbered). Moved effective date and Transmittal Letter processing from the National Flight Data Center (NFDC) responsibilities to AeroNav Products responsibilities. Also clarified that both textual and graphic ODPs will be incorporated into the Transmittal Letter and that SIDs and Diverse Vector Areas (DVA) will be submitted to NFDC for incorporation into the National Flight Data Digest (NFDD).

(25) Paragraph 2-1-2e(10). New (remaining paragraphs renumbered). Moved responsibility from NFDC to AeroNav Products.

(26) Paragraph 2-1-2e(11). New (remaining paragraphs renumbered). Added guidance to ensure completed airspace action prior to assigning an effective date.

(27) Paragraph 2-1-2e(12). New (remaining paragraphs renumbered). Added requirement to ensure “routine” procedures are flight inspected prior to incorporating the procedure into the Transmittal Letter.

(28) Paragraph 2-1-2g(2). Revised paragraph to support transfer of NFDC Transmittal Letter responsibilities to AeroNav Products; see paragraphs 7 thru 10, above. Added requirement to publish DVA in NFDD.

(29) Paragraphs 2-1-2g(3) thru (6) removed, paragraph numbering updated accordingly.

(30) Paragraph 2-1-2g. Updated guidance regarding AAUP.

(31) Paragraph 2-1-3. Revised paragraph to support AeroNav Products and NFDC responsibilities changes; re-lettered paragraph accordingly.

(32) Paragraph 2-1-4a. Editorial change, moving the Note guidance to the main body of the paragraph and converted what was in the main body to a Note.

(33) Paragraph 2-1-5a(5). Changed reference for AAUP guidance to a new paragraph.

(34) Paragraph 2-1-5d(2). Editorial change for consistency with instrument approach procedure cancellation process.

(35) Paragraph 2-1-6. Editorial change for clarity.

(36) Paragraph 2-1-6b(4)(k) Added. Added the ability to make heading/course/track number changes to support magnetic variation changes with abbreviated amendments.

(37) Paragraph 2-1-6c (New). Added guidance to address a DVA amendment.

c. Chapter 3.

(1) The former appendix A is now chapter 3.

f. Appendix D. › (2) Section 1, paragraph 11.

(2) Paragraph 3-1-1a. Editorial.

(3) Paragraph 3-1-1i. Revised to tie more closely to the SID definition in the Pilot/Controller Glossary.

(4) Paragraph 3-1-1j (new). Added guidance on Transitions and clarified that multiple Transitions may contain a common segment prior to branching off.

(5) Paragraph 3-1-1m. Removed reference to crossing altitudes.

(6) Paragraph 3-1-2d. Revised paragraph to return RNAV procedure naming to previous methods; i.e., “(RNAV)” adjacent to procedure name.

(7) Paragraph 3-1-4b. Clarified that a CID is optional for radar vector SIDs.

(8) Table 3-1-1, footnote 2. Added option for VA-VM-DF leg type combination.

(9) Table 3-1-1, footnote 9. Added regarding FM Legs.

(10) Paragraph 3-1-5d. Revised paragraphs to return RNAV procedure naming and chart notes to previous methods; i.e., Chart: “RNAV-1” or “RNP-1” as applicable.

(11) Paragraph 3-1-6. Broke examples out into separate paragraph and made editorial changes to match requirements specified throughout the order.

d. Appendix A.

(1) Appendix A is now “Administrative Information”; former appendix A is now chapter 3.

(2) Distribution requirements changed to “electronically only.”

(3) Added definition of “Service Providers.”

(4) Changed “Service Center” to “Service Area.”

(5) Paragraph 3p. Changed to “Least Onerous Method” and revised definition accordingly.

e. Appendix C. Updated instructions and data worksheet to match Order 8260.19 instructions.

f. Appendix D.

(1) Section 1, paragraph 9b. Expanded guidance on describing low, close-in obstacles.

(2) Section 1, paragraph 11.

h. Appendix F. › (1) Paragraph 3a(5) Added.

(3) Section 1, paragraph 18a. Editorial; “proposed” instrument procedures are no longer permitted under Order 8260.26F.

(4) Section 2, paragraph 2. Added requirement to enter “Special” if applicable.

(5) Section 2, paragraph 6b. Expanded guidance on describing low, close-in obstacles.

(6) Section 2, paragraph 9b. Added requirement to document reference magnetic variation to be consistent with the existing requirement in appendix E for RNAV departure procedures.

(7) Section 2, paragraph 20a. Editorial; “proposed” instrument procedures are no longer permitted under Order 8260.26F.

(8) Updated sample forms to correspond to various changes for documentation.

g. Appendix E.

(1) Section 1, paragraph 2. Added requirement to enter “Special” if applicable.

(2) Section 1, table E-1 Footnote*. Added guidance on turn direction application for DF legs after the first leg.

(3) Section 1, paragraph 3e Examples. Added guidance to support VA-VM-DF leg type combination.

(4) Section 1, paragraph 6. Expanded guidance on describing low, close-in obstacles.

(5) Section 1, paragraph 7. Added unique guidance regarding documenting controlling obstacles helicopter procedures.

(6) Section 1, paragraph 13. Broke into sub-paragraphs and added guidance for a chart note that directs the user to the AAUP.

(7) Section 1, paragraph 20a. Editorial; “proposed” instrument procedures are no longer permitted under Order 8260.26F.

(8) Updated sample forms to correspond to various changes for documentation.

(9) Section 2, paragraph 1j. Added requirement to document reference NAVAID for CF Legs.

(10) Section 3. Updated AAUP guidance.

h. Appendix F.

(1) Paragraph 3a(5) Added. Added requirement to insert “COPTER” in the “Type” line to indicate that these procedures are for helicopter operations only.

i. Appendix G. › (3) Paragraph 1h.

(2) Paragraph 3a(7)(a) and (b) Added. Added guidance for documenting Takeoff Obstacle notes for helicopter procedures that contains either a “visual segment” or a “VFR segment.”

(3) Paragraph 3a(8)(a) Added. Added requirement to chart a note to inform the pilot to use a specific altimeter source.

(4) Paragraph 3a(8)(c). Added, “CDI may be reset to 1.0 NM after (Fix Name).”

(5) Updated sample forms to correspond to various changes for documentation.

i. Appendix G.

(1) Paragraph 1e. Added new paragraph to provide guidance on charting the DVA to include required climb gradients where necessary and provided examples.

(2) Paragraph 1f. Formerly paragraph 1e; changed paragraph identification from “DVA” to read “For ATC Use Only.”

(3) Paragraph 1h. Added requirement to provide facility contact information in the event immediate changes need to be passed on immediately.

(4) Depict an ODP either textually or graphically within the following… › (a) Textual ODP.

Chapter 2. Responsibilities

Section 2-1.

2-1-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 (ATC) clearances [referred to as Standard Instrument Departure (SID)].

(1) Conduct a diverse departure assessment 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 Terminal Instrument Procedures (TERPS) Diverse Departure obstacle assessment is accomplished and an ODP developed, where applicable.

b. Obstacle Departure Procedures. Develop an ODP and/or non-standard takeoff minimums when obstructions penetrate the 40:1 departure obstacle clearance surface (OCS) as described in Order 8260.3, U.S. Standard for Terminal Instrument Procedures (TERPS), volume 4. Use table 2-1-1 as a guide to determine each situation and the required action. Use figures 2-1-1, 2-1-2, or 2-1-3 as an aid when applying the scenarios listed in table 2-1-1. 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-1 and associated figures that follow for recommended ODP development combinations and figure footnotes containing ODP text examples.

(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-1, apply “before rounding” values to each situation to determine required action.

(4) Depict an ODP either textually or graphically 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. Obstacle Departure Procedures. Develop an ODP and/or non-standard… › (12) Do not establish a VCOA maneuver in conjunction with an RNAV ODP.

(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 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-1-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) Develop ODPs with primary emphasis given to using the least onerous method (see appendix A) to get the aircraft 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, climb gradients, speed and/or altitude restrictions solely for ATC purposes are not allowed.

(8) Naming conventions and computer code assignments for graphic ODPs must follow the guidance specified for SIDs in chapter 3 to ensure controller awareness of route flown.

(9) Transition Routes are not permitted on ODPs.

(10) When applicable, develop ODPs using ground based NAVAIDs, area navigation (RNAV), or dead reckoning guidance wherever possible. Do not specify radar vectors 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, develop an RNAV ODP.

(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) Do not establish a VCOA maneuver in conjunction with an RNAV ODP.

b. Obstacle Departure Procedures. Develop an ODP and/or non-standard… › (15) Design graphic ODPs to terminate at a fix/NAVAID located within…

(13) The VCOA requirement in table 2-1-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 designed specifying a route must 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) Design graphic ODPs to terminate at a fix/NAVAID located within the IFR en route structure.

Table 2-1-1. ODP Development Combinations

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 Climb Gradient (CG) greater than 200 ft/NM to an altitude of 200 feet 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 feet 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 feet 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.

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 feet 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 feet 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 feet or less above DER and additional obstacles that require a CG to an altitude greater than 200 feet above DER.

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

Figure 2-1-1. Situation 3, Action A and Situation 2/4 (as applicable)

Penetrating obstacles located within the 3 SM ICA

Figure 2-1-1 Footnotes: 1. TAKEOFF MINIMUMS: “RWY 11, Standard.” TEXTUAL DEPARTURE PROCEDURE: (Leave blank) TAKEOFF OBSTACLE NOTES: “NOTE: RWY 11: (Enter obstacle notes)”

2. TAKEOFF MINIMUMS: “RWY 23, Standard.” TEXTUAL DEPARTURE PROCEDURE: “RWY 23 - Climbing right turn direct ABC VORTAC, continue climb in ABC holding pattern (hold east, left turns, 252.17 inbound) to cross ABC VORTAC at or above MEA for route of flight.” TAKEOFF OBSTACLE NOTES: “NOTE: RWY 23: (Enter obstacle notes)”

3. TAKEOFF MINIMUMS: “RWY 23, 300-1 ¼ or standard with minimum climb of 415 ft per NM to 2800.” TEXTUAL DEPARTURE PROCEDURE: “RWY 23 - Climbing right turn direct ABC VORTAC, continue climb in ABC holding pattern (hold east, left turns, 252.17 inbound) to cross ABC VORTAC at or above MEA for route of flight.” TAKEOFF OBSTACLE NOTES: “NOTE: RWY 23: (Enter obstacle notes)”

4. TAKEOFF MINIMUMS: “RWY 27, 300-1 or standard with minimum climb of 275 ft per NM to 2100.” TEXTUAL DEPARTURE PROCEDURE: (Leave blank) TAKEOFF OBSTACLE NOTES: “NOTE: RWY 27: (Enter obstacle notes)”

5. TAKEOFF MINIMUMS: “RWY 36, 300-2 or standard with minimum climb of 225 ft per NM to 600, or alternatively with standard takeoff minimums and a normal 200 ft per NM climb gradient, takeoff must occur no later than 1800 ft prior to DER.” TEXTUAL DEPARTURE PROCEDURE: “RWY 36 - (Specify departure procedure or leave blank for diverse)” TAKEOFF OBSTACLE NOTES: “NOTE: RWY 36: (Enter obstacle notes)”

Graphic ODP in lieu of Textual ODP TAKEOFF MINIMUMS: (Blank) TEXTUAL DEPARTURE PROCEDURE: “RWY 23 - Use ALPHA departure.” TAKEOFF OBSTACLE NOTES: (Blank)

Figure 2-1-2. Situation 3, Action B Penetrating obstacles located outside the 3 SM ICA

Figure 2-1-2 Footnotes: 1. TAKEOFF MINIMUMS: “RWY 36, Standard.” TEXTUAL DEPARTURE PROCEDURE: “RWY 36 - Climb on heading 357.11 to 2800 before turning right.”

2. TAKEOFF MINIMUMS: “RWY 8, Standard with minimum climb of 390 ft per NM to 11800, or 5300-3 for VCOA.” TEXTUAL DEPARTURE PROCEDURE: “RWY 8 - Climb on XYZ VOR/DME R-081 TO ALPHA, then climbing left turn direct XYZ VOR/DME, continue climb in XYZ holding pattern (hold east, right turns, 263.57 inbound) to cross XYZ VOR/DME at or above MEA for route of flight. VISUAL CLIMB OVER AIRPORT: Obtain ATC approval for VCOA when requesting IFR clearance. Climb in visual conditions to cross Metro Airport at or above 10800 before proceeding on course.”

3. TAKEOFF MINIMUMS: “RWY 36, Standard with minimum climb of 355 ft per NM to 7700, or 3800-3 for VCOA.” VISUAL CLIMB OVER AIRPORT: “RWY 36 – Obtain ATC approval for VCOA when requesting IFR clearance. Climb in visual conditions to cross Downtown Airport at or above 9200 before proceeding on course.”

4. TAKEOFF MINIMUMS: “RWY 8, Standard with minimum climb of 220 ft per NM to 10700 or alternatively, with standard takeoff minimums and a normal 200’ per NM climb gradient, takeoff must occur no later than 1600’ prior to DER or 5300-3 for VCOA.” TEXTUAL DEPARTURE PROCEDURE: “RWY 8 - (Specify departure procedure, OR for diverse, leave blank)” VISUAL CLIMB OVER AIRPORT: Obtain ATC approval for VCOA when requesting IFR clearance. Climb in visual conditions to cross (instructions as required based on decision above) before proceeding on course.” Graphic ODP in lieu of Textual ODP TAKEOFF MINIMUMS: (Blank) TEXTUAL DEPARTURE PROCEDURE: “RWY 23 - Use ALPHA departure.” TAKEOFF OBSTACLE NOTES: (Blank)

Figure 2-1-3. Situation 3, Action C and Situation 4 Penetrating obstacles located within AND outside the 3 SM ICA that require a non-standard climb gradient (Diverse & Route/Sector)

Figure 2-1-3 Footnotes:

1. TAKEOFF MINIMUMS: “RWY 11, 400-2 or standard with minimum climb of 250 ft per NM to 3000.” TEXTUAL DEPARTURE PROCEDURE: “RWY 11 - Climb on heading 112.90 to 3700 before turning right.” TAKEOFF OBSTACLE NOTES: “NOTE: RWY 11: (Enter notes for obstacles located within the 3 SM ICA)”

2. TAKEOFF MINIMUMS: “RWY 5, 300-1¼ with minimum climb of 350 ft per NM to 6000 or standard with minimum climb of 500’ per NM to 5000 or 2100-3 for climb in visual conditions.” TEXTUAL DEPARTURE PROCEDURE: “RWY 5 - (Specify departure procedure, OR for diverse, leave blank)” VISUAL CLIMB OVER AIRPORT: Obtain ATC approval for VCOA when requesting IFR clearance. Climb in visual conditions to cross (instructions as required based on decision above) before proceeding on course. TAKEOFF OBSTACLE NOTES: “NOTE: RWY 5: (Enter notes for obstacles located within the 3 SM ICA)”

3. TAKEOFF MINIMUMS: “RWY 5, Standard with minimum climb of 425 ft per NM to 5400 or 2100-3 for climb in visual conditions.” TEXTUAL DEPARTURE PROCEDURE: “RWY 5 - (Specify departure procedure, OR for diverse, leave blank)” VISUAL CLIMB OVER AIRPORT: Obtain ATC approval for VCOA when requesting IFR clearance. Climb in visual conditions to cross (instructions as required based on decision above) before proceeding on course. TAKEOFF OBSTACLE NOTES: “NOTE: RWY 5: (Enter notes for obstacles located within the 3 SM ICA)”

4. TAKEOFF MINIMUMS: “RWY 11, 400-2 or standard with minimum climb of 220 ft per NM to 3400 or alternatively, with standard takeoff minimums and a normal 200 ft per NM climb gradient, takeoff must occur no later than 1200 ft prior to DER.” TEXTUAL DEPARTURE PROCEDURE: “RWY 11 - Climb on heading 115.90 to 3700 before turning right.” TAKEOFF OBSTACLE NOTES: “NOTE: RWY 11: (Enter notes for obstacles located within the 3 SM ICA)”

5. TAKEOFF MINIMUMS: “RWY 5, 300-2 with minimum climb of 210 ft per NM to 5100 or standard with minimum climb of 225 ft per NM to 4200 or alternatively with standard takeoff minimums and a normal 200 ft per NM climb gradient, takeoff must occur no later than 1500 ft prior to DER or 1700-2 for VCOA.” TEXTUAL DEPARTURE PROCEDURE: “RWY 5 - (Specify departure procedure, OR for diverse, leave blank)” VISUAL CLIMB OVER AIRPORT: Obtain ATC approval for VCOA when requesting IFR clearance. Climb in visual conditions to cross (instructions as required based on decision above) before proceeding on course. TAKEOFF OBSTACLE NOTES: “NOTE: RWY 5: (Enter notes for obstacles located within the 3 SM ICA)”

Graphic ODP in lieu of Textual ODP TAKEOFF MINIMUMS: (Blank) TEXTUAL DEPARTURE PROCEDURE: “RWY 23 - Use ALPHA departure.” TAKEOFF OBSTACLE NOTES: (Blank)

d. Design Constraints. The following design constraints apply to all… › (3) Specify speed restrictions only when necessary to ensure obstacle…

c. Standard Instrument Departures (SIDs). Develop SIDs 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 depict 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) Design SIDs 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 or a course to be flown at the termination point, provide a heading/course 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 feet above the departure end of runway (DER) elevation. See Order 8260.3, volume 4, and Order 8260.58, United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design, when a turn is required within two nautical miles (NM) of departure end runway (DER).

(2) Flight Standards Service or appropriate Department of Defense (DoD) authority must approve DPs requiring a climb gradient (CG) in excess of 500 ft/NM (600 ft/NM for helicopters). Approval requests will be assessed by the FAA Flight Technologies and Procedures Division (AFS-400), Procedures Review Board (PRB).

Note: Base consideration for approval 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 CGs 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 AFS will not approve a 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 statute miles (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 AFS will not approve a 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.

(3) Specify speed restrictions only when necessary to ensure obstacle clearance, airspace efficiency during turns, or when necessary to achieve an operational advantage. Refer to applicable DP criteria directives.

(1) Charting Altitudes. Document altitudes for charting as follows: › (c) When an ATC has requested an “at or below” altitude restriction at…

(a) Speed restrictions to support ATC requirements are only allowed in SID design and must not be included in ODPs.

(b) Limit speed restrictions [except as noted in paragraph 2-1-1d(3)(c)] 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.”

(4) Do not use fan markers 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 (lateral or vertical) from the end of a runway to the end of the DP, to support different types of aircraft (i.e., jet, turbo-prop, etc.) or different equipment requirements [distance measuring equipment (DME), non DME]. Where this is necessary, develop separate procedures.

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, do not depict ATC required altitudes on ODPs.

(b) When ATC requests a minimum “at or above” altitude restriction 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)].

Note: When establishing crossing altitudes for other than meeting obstacle clearance and/or lateral navigation (LNAV) engagement altitude requirements, stakeholders should give consideration to aircraft performance limitations based on the type of aircraft expected to be using the SID and whether those aircraft will be capable of meeting these altitude restrictions. This may require consultation with “lead carriers,” local operators, and/or industry associations that could be impacted.

(c) When an ATC has requested an “at or below” altitude restriction at a fix, 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

in conjunction with the “at or below” altitude at the same fix making this either a “mandatory” or “block” fix crossing altitude. See note in paragraph 2-1-1e(1)(b).

e. Charting Constraints. The following charting constraints apply: › (4) ODPs depicted graphically must have the term “(OBSTACLE)” printed…

(d) When ATC requests an altitude restriction for a fix located on a transition route, it must be at or above the specified minimum en route altitude (MEA) for the route. See note in paragraph 2-1-1e(1)(b).

(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 CG exceeding 200 ft/NM [400 ft/NM for helicopters beginning at the initial departure fix (IDF)] whenever required for obstruction clearance and include the altitude to which the gradient is required in the Takeoff Minimums note; e.g., “(Takeoff minimums) with minimum climb of 300 ft/NM to 4300.” Do not establish CGs for crossing altitudes used to support airspace, environmental, or ATC operational limitations. When a CG is required to support an LNAV engagement altitude (e.g., 500 ft/NM to 1300) before turning, a reduced, second CG may be established in this situation only (i.e., a maximum of two CGs). See applicable 8260-series orders for the appropriate criteria to use when establishing a minimum CG. Enter minimum CG and associated termination altitude for charting on the appropriate 8260-15 series form (see appendix D, E, or F).

Note: Helicopter Point in Space IFR departures depart VFR (or may depart visually for approved Special procedures) from a heliport/departure surface, to the IDF. The departure is considered as beginning at the IDF for departures that do not contain a “visual segment” (see appendix F, paragraph 2). The climb gradient for helicopter departures is normally much greater to the IDF after which the CG is reduced to (typically) the standard CG of 400 ft/NM in the 20:1 area.

(3) Charting Speed Restrictions. Identify required speed restrictions 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) Annotate speed restrictions for graphic ODPs and SIDs on the chart at the restriction point; in the Additional Flight Data block of Form 8260-15B, document the speed restriction as follows: CHART SPEED ICON (Maximum/Minimum/Mandatory) SPEED (value) KIAS AT (Fix Name). State speed restrictions not associated with a fix in the form of a chart note; e.g., “Chart Note: Do not exceed 210 KIAS until established direct ABC VOR.”

(4) ODPs depicted graphically must have the term “(OBSTACLE)” printed on the graphic (see appendix D or E). Indicate 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).

g. Terminology. The following terminology applies for initial climb… › (3) If departure instructions require a specific altitude to climb to…

(5) ODPs developed for RNAV use must have the terms (OBSTACLE) and (RNAV) printed on the graphic. Indicated by the words “OBSTACLE” and “RNAV” adjacent 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-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 omnidirectional 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. Do not require automated vertical navigation.

(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. Annotate SIDs requiring radar vectors with “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.” Procedure developers will update these procedures during the periodic review process, changing the terminology to specify the actual heading to be 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 (hundredths of a degree are not used in ATC communications).

(2) If departure instructions require ATC to assign a heading, use: “Climb on assigned heading for radar vectors to (name of fix/airway, etc.).”

(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 …”

i. Attention All Users Page. For simultaneous RNAV departures, an AAUP… › (2) AAUP Preparation.

(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 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 to heading 280, 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 used on nonstandard departure procedures approved by Flight Standards or the appropriate military authority.

h. Diverse Vector Area (DVA). An ATC facility may request a DVA 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-8-5, Establishing Diverse Vector Areas. Order 8260.3, contains the criteria used for development. See appendix G of this order for documenting the development of a DVA.

i. Attention All Users Page. For simultaneous RNAV departures, an AAUP must be published. The AAUP provides the flight crew with procedures that must be used when conducting these operations, in a form that may be reviewed prior to conducting the procedure.

Note: The flight crew will be notified when an AAUP is published. The note will appear on the narrative page immediately beneath the Departure Route Description title. See appendix E, section 1, paragraph 13d.

(1) Site Implementation Team (SIT). A SIT is normally established to address issues related to establishing the procedures. If no team is established, the FAA facility that provides ATC services for the airport at which the operations are to be conducted is responsible for the AAUP. The SIT is:

(a) Comprised of FAA and industry members with the team leadership designated by ATO.

(b) Responsible for the development, among other things, of an AAUP.

(2) AAUP Preparation. The AAUP must present the step-by-step procedures used to conduct the procedure. Develop the AAUP using Form 8260-15E and the guidance provided in appendix E, section 3.

Note: An AAUP example is provided in appendix E and may not be the most current or not necessarily applicable to other locations. This example should be used as a developmental

a. General. The following guidance outlines procedures for DP requests,… › (2) Requirements.

guideline. AAUPs must reflect the requirements of the specific procedure and airport for which they are developed.

(3) AAUP Processing. The SIT (or applicable ATC facility) submits the draft AAUP through channels as applicable (that is, Service Areas may have a coordination process unique to their area). Also, submit the procedure to AJV-14 for comment. When completed, submit the procedure to the Flight Technologies and Procedures Division (AFS-400) for approval. Also, provide a copy to Flight Standards’ Flight Operations Branch (AFS-410) and the Performance- Based Flight Operations Branch (AFS-470). AFS-400 submits the AAUP and requested effective date to the National Flight Data Center (NFDC).

(4) AAUP Publication. The originating organization will determine the required publication date; coordinate with AeroNav Products and NFDC as necessary. After receiving the AAUP from AFS-400, NFDC will:

(a) Verify the applicability of the publication date and assign that date for publication.

(b) Coordinate with AFS-400 who will, in turn, contact the originating organization and AeroNav Products should a change in the previously agreed upon date be required.

Note: When publishing a new AAUP in conjunction with a new or revised procedure, it is important that the AAUP be coordinated jointly between the originating organization, NFDC, AeroNav Products, and AFS-400 to ensure its publication is concurrent with the procedure(s) for which the AAUP was developed.

(c) Publish the AAUP in the National Flight Data Digest (NFDD).

Note: The NFDD is the source for AAUP information for publication by all chart producers. 2-1-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. Process all requests for new or amended SIDs 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 requirements, AeroNav

c. ATC. When assisting a proponent or requesting a SID, the ATC… › (4) Coordinate with the servicing Air Route Traffic Control Center…

Products, Flight Procedure Standards Branch (AFS-420), and other ATO organizations/involved parties must work together to find an acceptable solution.

(3) Cancellation. The RAPT must approve all proposed SID cancellations. 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. Complete and forward this information 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.

(4) The Air Traffic Organization (ATO) is responsible for satisfying the requirements for FAA Order 1100.161 paragraph 3-2, Air Traffic Safety Oversight, Safety Risk Management Program for changes to the National Airspace System (NAS).

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) Coordinate with the servicing Air Route Traffic Control Center (ARTCC) to obtain a 5-letter pronounceable name for all fixes in the graphic DP. Complete Form 8260-2, Radio Fix and Holding Data Record, 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.

d. Service Area Operations Support Group. The Service Area Operations… › (8) The OSG-FPT notifies the requesting ATC facility of the anticipated…

(5) Coordinate with the servicing ARTCC to obtain a name and computer code for the SID as specified in chapter 3.

(6) Complete the DP requirements data worksheet (see appendix B), when applicable.

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

(8) Review SIDs at least biennially for continued need. Coordinate requested changes through the applicable Service Area Operations Support Group, Flight Procedures Team.

(9) 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 paragraph 2-1-1i for additional guidance.

d. Service Area Operations Support Group. 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) Act as the focal point for all ATC coordination and provide appropriate assistance in resolving any problems identified during the development process.

(4) 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 JO 7470.1, DME/DME Infrastructure Evaluation for Area Navigation (RNAV) Routes and Procedures.

(5) Facilitate discussion of the procedure at the RAPT.

(6) Forward the DP package to AeroNav Products.

(7) Provide one copy of each FAA 8260-2 and 8260-15 series form(s) to all affected ATC facilities.

(8) The OSG-FPT notifies the requesting ATC facility of the anticipated publication date and any delay in the publication and cause.

e. AeroNav Products. AeroNav Products must: › (13) Review ODPs periodically for continued need, obstacle clearance,…

(9) The OSG-FPT must ensure that changes to the National Airspace System (NAS) comply with FAA Order 1100.161, paragraph 3-2, Safety Risk Management Program.

e. AeroNav Products. 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) After satisfactory flight inspection, forward the original Form(s) 8260-2 and original 8260-15 series forms to NFDC. Copies are available for distribution [see paragraph 2-1-2d(5)].

(8) Develop, review, track, and cancel Notices to Airmen (NOTAMs) relating to ODPs and SIDs.

(9) Assign an effective date for all ODPs and SIDs. Publish both textual and graphic ODPs in the Transmittal Letter (TL) authorizing charting agencies to publish the procedure(s). Submit SIDs and DVAs to the NFDC for incorporation into the National Flight Data Digest (NFDD).

(10) 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.

(11) Ensure related controlled airspace actions as required by Order JO 7400.2, Procedures for Handling Airspace Matters, have been completed prior to assigning an effective date.

(12) Ensure “routine” procedures have been flight inspected prior to incorporation in the TL.

(13) 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.

g. National Flight Data Center (NFDC). The NFDC must: › (2) Publish SIDs, associated fixes, AAUPs, and DVAs in the daily NFDD…

(14) 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.

(15) When it is necessary to cancel a DP, process the appropriate Form 8260-15 as directed in paragraph 2-1-5d.

(16) Add the “T” symbol to the 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.

(17) 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.

(18) Issue P-NOTAMs to correct U.S. Government charting discrepancies and compilation errors required (see Order 8260.19).

f. Flight Inspection Services. 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. National Flight Data Center (NFDC). The NFDC must:

(1) Conduct a 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) Publish SIDs, associated fixes, AAUPs, and DVAs in the daily NFDD authorizing charting agencies to publish these procedures. See paragraph 2-1-1i(4) for more specific AAUP responsibilities.

2-1-4. Military Departure Procedures (DPs). › d. When a military DP has a climb gradient established to clear…

(3) Resolve data conflicts, form discrepancies, etc., with AeroNav Products.

(4) File and maintain the original signed copy of the forms.

2-1-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 AeroNav products whenever pre-publication errors are discovered in the TL. AeroNav Products will coordinate necessary corrective actions with the NFDC and promulgate corrected data/forms.

c. Notify the NFDC whenever pre-publication errors are discovered in the NFDD. The NFDC will coordinate necessary corrective actions with AeroNav Products and promulgate corrected data/forms.

d. Notify AeroNav Products whenever charting discrepancies/compilation errors are detected in United States government published aeronautical products. AeroNav Products will coordinate corrective actions with NFDC.

2-1-4. Military Departure Procedures (DPs).

a. Military DPs. Name and number all military DPs in accordance with the criteria outlined in this order.

Note: 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.

b. The FAA requires that all military DPs be coordinated with FAA ATC facilities or regions when such DPs affect the National Airspace System (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.

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), the procedure must be annotated “NOT FOR CIVIL USE.”

2-1-5. FAA 8260-15 Series Forms (see appendices D through G). › b. Use Form 8260-15A/B to deny lower than standard takeoff minimums.…

2-1-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 to document:

(a) Standard takeoff minimums.

(b) Nonstandard takeoff minimums and/or higher than standard climb gradients for a runway.

(c) Textual ODPs.

(d) That the ODP for a runway is published graphically.

(e) Other pertinent textual data for publication; e.g., obstacle data notes, VCOA data, etc.

(2) Use Form 8260-15B to document:

(a) Graphically depicted complex ODPs and all SIDs.

(b) 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.

(4) Use Form 8260-15D to document a Diverse Vector Area (DVA).

(5) Use Form 8260-15E to document RNAV Departure Procedure AAUPs for locations where it has been determined that detailed departure information is necessary. See paragraph 2-1-1i for AAUP guidance.

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 feet, 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.”

a. Textual ODPs. › (1) When completing a full amendment, advance the amendment number in…

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 Standards 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 “Procedure 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).

2-1-6. Procedure Amendments. Amend all departure procedures 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 as applicable (and 8260-15C, if an RNAV procedure) for processing (see note 2). 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. Submit departure procedures not developed and/or not flight inspected by the FAA are 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/ validation. Specify this exception (or exceptions) in either an FAA directive or policy memorandum controlled by the flight inspection/validation authority. Provide AFS-460 a copy of all policy memorandums between flight inspection and procedure developers.

Note 2: When the abbreviated amendment process is used, take steps to ensure 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.

(4) Use an abbreviated amendment whenever a change is made to the items… › (j) Altitude changes (RNAV procedures require RNAV-PRO assessment when…

(2) Use P-NOTAMs to 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).

b. Graphic ODPs and SIDs.

(1) Whenever changing the “DP Name” in the title line of the Form 8260-15B, or changing the procedure “Type,” cancel the procedure and develop a new procedure.

(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 paragraph 3-1-2f.)

(3) Require a full amendment 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) Use an abbreviated amendment whenever a change is made to the items listed below as specified on Form 8260-15B. Do not use a P-NOTAM to effect an abbreviated amendment for graphic ODPs and SIDs.

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

2-1-6. Procedure Amendments. › c. DVA. Any change to a DVA is considered an amendment and requires a…

(k) Heading/course/track number changes made to support a magnetic variation update that does not alter the ground track of the existing procedure.

(5) An amendment is not 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; note the change in the procedure package historical information and retain 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).

c. DVA. Any change to a DVA is considered an amendment and requires a new Form 8260-15D to be generated, establishing a new amendment number.

THIS PAGE INTENTIONALLY LEFT BLANK

l. Altitude. › (2) Minimum and maximum “block” altitudes for the same fix/waypoint are…

Chapter 3. Guidelines for the Design of Graphic Instrument Departure Procedures (DPs)

Section 3-1.

3-1-1. General.

a. 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 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. A SID must be designed to terminate at a fix/NAVAID located within the IFR en route structure, at an altitude that will allow random IFR flight, or at a position where ATC radar service is provided.

j. A Transition may be developed from the end of a SID to support a need to take aircraft to additional fixes/NAVAIDs depicted on an IFR en route chart. A SID may contain multiple transitions and may share a common segment prior to branching off into multiple directions.

k. Avoid Speed Restrictions Whenever Possible. See paragraphs 2-1-1d(3) and 2-1-1e(3) for specific guidance.

l. 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-1-1e(1) for specific guidance and charting constraints.

3-1-2. Naming of DPs (see examples at the end of this chapter). › e. If two or more DPs end at the same fix/NAVAID, the second and…

(3) Do not use 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 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.

m. Climb Gradient. 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/or LNAV engagement altitude [see paragraphs 2-1-1d(2) and 2-1-1e(2) for specific guidance].

3-1-2. Naming of DPs (see examples at the end of this chapter).

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. If the DP is an RNAV procedure, the “(RNAV)” must be included in the name; for example, TATES TWO DEPARTURE (RNAV). See appendix E to see how this will be documented for RNAV procedures.

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

a. Waypoints. Specify all waypoints as either fly-by or fly-over. › (3) Design procedures using the fewest number of waypoints.

f. Number Each Original Graphic DP “ONE.” Number subsequent amendments in numerical sequence through NINE and then start over with ONE (see paragraph 2-1-6b for the amendment process).

3-1-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.

3-1-4. Computer Identification Codes. See pages appendix B for examples.

a. Textual ODPs. 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 paragraph 3-1-2d is coded “CVG8.CVG”; the FORT LAUDERDALE SEVEN DEPARTURE in paragraph 3-1-3 is coded “FLL7.FLL”; and the “TATES TWO DEPARTURE in paragraph 3-1-2d is coded “TATES2.TATES.” A computer identification code is not required and; therefore, optional 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.

Note: In order to determine if a Computer Identification Code is to be established for a new (or can be removed from an existing) radar vector SID, the applicable ATC facility must be contacted to “confirm” what action is desired.

c. SID Transition. SID transition computer codes are assigned by using the SID identifier and number as noted in paragraph 3-1-4b, followed by a dot, followed by the identifier of the en route fix where the transition ends. Using the Fort Lauderdale example in paragraph 3-1-3, the ZAPPA transition is coded “FLL7.ZAPPA.” Using the REDSS example in paragraph 3-1-3, the Johnstown transition is coded “REDSS4.JST.

3-1-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.

(3) Design procedures using the fewest number of waypoints.

3-1-5. RNAV DPs. › b. Leg Types. Table 3-1-1 shows permissible leg types for use with RNAV…

b. Leg Types. Table 3-1-1 shows permissible leg types for use with RNAV DPs. See Order 8260.58 for leg type definitions and examples.

Table 3-1-1. Permissible Leg Types

FROM VIA (leg type) TO

AER VI1 See 1

AER VA2 ALT

AER VM8 HDG

AER CF3, DF4 FB/FO

ALT CF3, DF4 FB/FO

ALT VM2 ALT

FB TF5 FB/FO

FO DF4, TF5 FB/FO

IF7 DF4, TF5 FB/FO

FB RF6 FB

FO VM8 HDG

FO FM9 Course 1 VI (Heading-to-intercept) may only be used as the first leg of a departure and must be followed by a course-to-fix (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 direct-to-fix (DF) leg or a heading-to-manual termination (VM) to 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. 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 fly-over (FO) waypoint (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.

d. Chart Annotation. › (6) When an “RNP 1” DP contains a radius-to-fix (RF) leg or all…

8 VM (Heading-to-manual termination) legs are only to be used in conjunction with ATC radar vectoring. 9 FM (Course from a fix-to-manual termination) legs are used when requested by ATC and can only be placed at the end of a SID and must be at an altitude at or above the minimum vectoring altitude or minimum IFR altitude for direction of flight. 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) “RNAV-1” will be the default designation for RNAV DPs. Annotate procedures with a standard note: “RNAV-1” on FAA Form 8260-15B (see appendix E).

(2) “RNP-1” (in-lieu-of RNAV-1) will be used when a DP that contains an RF leg or when surveillance (Radar) monitoring is not desired for when DME/DME/IRU will be used. Annotate the procedure with a standard note: “RNP-1” on FAA Form 8260-15B (see appendix E).

(3) All RNAV 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.

(4) 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.

(5) Except as required by paragraph 2-1-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.”

(6) 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

Section 3-1. › 3-1-6. Examples of Various Graphic Departure Scenarios.

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.

3-1-6. Examples of Various Graphic Departure Scenarios.

EXAMPLES:

EXAMPLES (Continued):

EXAMPLES (Continued):

EXAMPLES (Continued):

THIS PAGE IS INTENTIONALLY LEFT BLANK

3. Definitions. › f. Departure Procedure (DP). A preplanned IFR departure procedure…

05/30/2014 8260.46E Appendix A

Appendix A. Administrative Information

1. Distribution. This order is distributed electronically only.

2. Background. The original order combined into a single product, textual instrument flight rule (IFR) departure procedures that were developed by the AeroNav Products under the guidance of the Flight Standards Service (AFS), and graphic standard instrument departures (SIDs) that were designed and produced under the direction of the Air Traffic Organization (ATO) into a single product. This combined product introduced the new acronym, Departure Procedures (DP), to the pilot/controller community and the aforementioned terms of “IFR departure procedure,” and “SID” were eliminated. The original order also provided for the graphic publication of IFR departure procedures (DP) to facilitate pilot understanding of the procedure as well as all area navigation (RNAV) and required navigation performance (RNP) DPs, both those developed solely for obstruction clearance and those developed for system enhancement. Elimination of the term “SID” created undue confusion in both the domestic and international aviation communities. Therefore, in the interest of international harmonization, the FAA reintroduced the term “SID” in Order 8260.46B while also using the term “Obstacle Departure Procedures (ODPs)” to describe certain procedures. This order defines two separate types of DPs: SIDs and ODPs and provides policy guidance for the development and documentation of each.

3. Definitions. As used in this order shall or must mean compliance is mandatory. All references to related Orders and Publications apply to the latest edition. A glossary of additional terms, abbreviations, and acronyms used in this order:

a. Approach End of Runway (AER). The first portion of the runway available for landing. If the runway threshold is displaced, use the displaced threshold Lat/Long as the AER.

b. Area Navigation (RNAV). A system of enhanced navigational capability that can compute aircraft position, actual track and ground speed, and then provide meaningful information relative to the route of flight selected by the pilot.

c. Climb Gradient (CG). A climb requirement expressed in feet per NM (gradient greater than 200 ft/NM).

d. Controller Chart. An aeronautical chart developed for internal air traffic controller reference in specific ATC facilities. These charts may also be used to design instrument procedures to support ATC operations.

e. Departure End of Runway (DER). The end of the runway that is opposite the landing threshold. It is sometimes referred to as the stop end of the runway.

f. Departure Procedure (DP). A preplanned IFR departure procedure published for pilot use, in graphic or textual format, that provides obstruction clearance from the terminal area to the en route structure. There are two types of DPs - Obstacle Departure Procedures (ODP) printed either textually or graphically, and Standard Instrument Departure (SID), which is always printed graphically.

3. Definitions. › s. Navigational Aid (NAVAID). See Aeronautical Information Manual…

05/30/2014 8260.46E Appendix A

g. Diverse Vector Area (DVA). An area in a radar environment established at the request of Air Traffic, and jointly developed with the FPT, that meets TERPS criteria for diverse departures, obstacles and terrain avoidance in which random radar vectors below the MVA/MIA may be issued to departing aircraft.

h. Electronic Transmission. Transmittal via electronic mail (e-mail) or facsimile (fax).

i. Fix. A generic term used to define a predetermined geographical position used for route definition. A fix may be a ground-based NAVAID, a waypoint, or defined by reference to one or more radio NAVAIDs.

j. Flight Procedures Team (FPT). An element of Mission Support Services, geographically located in each Air Traffic Service Area.

k. Fly-By Waypoint. A fly-by waypoint requires the use of turn anticipation to avoid overshoot of the next flight segment.

l. Fly-Over Waypoint. A fly-over waypoint precludes any turn until the waypoint is overflown and is followed either by an intercept maneuver of the next flight segment or direct flight to the next waypoint.

m. Initial Climb Area (ICA). An area beginning at the departure end of runway (DER) to provide unrestricted climb to at least 400 feet above DER elevation.

n. Initial Departure Fix (IDF). The first published fix/waypoint used for the departure. The IDF denotes the beginning of the RNAV portion of the SID.

Note: “IF” is used for coding (per ARINC 424) of the IDF. “IF” or “IDF” will not be placed on a departure chart in order to prevent confusion. The “IF” acronym is also used in conjunction with the intermediate fix of an instrument approach procedure.

o. Lead Carrier. An air carrier or operator that has agreed to serve as the focal point for the development of DPs at a specific airport. The lead carrier agrees to help develop the DP and conducts initial flyability evaluations by all RNAV-equipped aircraft expected to use the DP.

p. Least Onerous Method. The use of obstacle DP criteria standards to clear terrain or other obstacles that will result in the lowest possible climb gradient for that runway.

q. National Flight Data Center (NFDC). The FAA office responsible for the collection, validation, and dissemination of all aeronautical information relating to the NAS.

r. National Flight Data Digest (NFDD). A daily publication, prepared by the NFDC to promulgate non-regulatory changes to the NAS.

s. Navigational Aid (NAVAID). See Aeronautical Information Manual (AIM). Any visual or electronics device airborne or on the surface which provides point-to-point guidance information or position data to aircraft in flight.

3. Definitions. › ee.

05/30/2014 8260.46E Appendix A

t. Non-RNAV DP. A DP whose ground track is based on ground-based NAVAIDs and/or dead reckoning navigation.

u. Obstacle Clearance Surface (OCS). An inclined surface associated with a defined area for obstruction evaluation.

v. Obstacle Departure Procedure (ODP). A preplanned IFR departure procedure printed for pilot use in textual or graphic form to provide obstruction clearance via the least onerous route from the terminal area to the appropriate en route structure. ODPs provide obstruction clearance and may be flown without ATC clearance unless an alternate departure procedure (SID or radar vector) has been specifically assigned by ATC.

w. Proponent. The originator of a DP requirement. This may include an individual user group, ATC, AeroNav Services, or other appropriate government agency.

x. Radar SID. A SID established when ATC has a need to vector aircraft on departure to a particular ATS Route, NAVAID, or fix.

y. Regional Airspace and Procedures Team (RAPT). A team established for the purpose of coordinating and processing requests for new or modified flight procedures and related airspace matters (see Order 8260.43).

z. RNAV DP. A DP developed for RNAV-equipped aircraft whose ground track is based on satellite or distance measuring equipment (DME)/DME navigation systems.

aa. Required Navigation Performance (RNP). A statement of the navigational performance accuracy necessary for operation within defined airspace. See the AIM for current definition.

bb. Runway Heading. The magnetic direction that corresponds with the runway centerline extended, not the painted runway numbers on the runway. Pilots cleared to “fly or maintain runway heading” are expected to fly or maintain the published heading that corresponds with the extended centerline of the departure runway (until otherwise instructed by ATC), and are not to apply drift correction; e.g., RWY 4, actual magnetic heading of the runway centerline 044.22 degrees, fly 044 degrees.

cc. Service Providers. Any organization, company, or person who develops Instrument Procedures.

dd. SID Transition. A published segment used to connect the SID to one or several en route airways/jet routes.

ee. Significant Benefits. Tangible or intangible advantages resulting from the implementation of a DP such as fuel savings from reduced flight tracks and time, reduced inter-/intra-facility coordination, reduced communications between ATC and pilots, increased flexibility of airspace management and sectorization due to more predictable ground tracks, or other similar benefits to users or providers.

a. FAA Orders and Advisory Circulars. › (8) Order 8260.3, United States Standard for Terminal Instrument…

05/30/2014 8260.46E Appendix A

ff. Standard Instrument Departure (SID). A preplanned IFR ATC departure procedure printed in graphic form for pilot/controller use to provide obstacle clearance and a transition from the terminal area to the appropriate en route structure. SIDs are primarily designed for system enhancement to expedite traffic flow and to reduce pilot/controller workload. ATC clearance must be received prior to flying a SID.

gg. Terminal Area Route Generation Evaluation and Traffic Simulation (TARGETS). An air traffic tool for RNAV DP design.

hh. Transmittal Letter (TL). A biweekly publication, prepared by the NFDC, used as the medium to promulgate instrument approach procedures and textual ODPs and their effective dates for publication.

ii. Visual Climb Over Airport (VCOA). A departure option for an IFR aircraft, operating in visual meteorological conditions equal to or greater than the specified visibility and ceiling, to visually conduct climbing turns over the airport to the published “climb-to” altitude from which to proceed with the instrument portion of the departure. VCOA procedures are developed to avoid obstacles greater than 3 statute miles (SM) from the departure end of the runway as an alternative to complying with climb gradients greater than 200 ft/NM. These procedures are published in the ‘Takeoff Minimums and (Obstacle) Departure Procedures’ section of the Terminal Procedures Publications or as an option on a Graphic ODP.

jj. Waypoint (WP). A predetermined geographical position used for route definition and/or progress reporting purposes defined by latitude/longitude and may include elevation.

4. Related Publications.

a. FAA Orders and Advisory Circulars.

(1) Advisory Circular 90-100, United States Terminal and En route Area Navigation (RNAV) Operations.

(2) Advisory Circular 90-105, Approval Guidance for RNP Operations and Barometric Vertical Navigation in the U.S. National Airspace System.

(3) Order 1100.161, Air Traffic Safety Oversight.

(4) Order 7100.9, Standard Terminal Arrival Program and Procedures.

(5) Order 7210.3, Facility Operation and Administration.

(6) Order 7400.2, Procedures for Handling Airspace Matters.

(7) Order JO 7470.1, DME/DME Infrastructure Evaluation for Area Navigation (RNAV) Routes and Procedures.

(8) Order 8260.3, United States Standard for Terminal Instrument Procedures.

Appendix A. Administrative Information › 6. Information Update.

05/30/2014 8260.46E Appendix A

(9) Order 8260.19, Flight Procedures and Airspace.

(10) Order 8260.26, Establishing and Scheduling Standard Instrument Procedure Effective Dates.

(11) Order 8260.42, United States Standard for Helicopter Area Navigation.

(12) Order 8260.43, Flight Procedures Management Program.

(13) Order 8260.53, Standard Instrument Departures that Use Radar Vectors to Join RNAV Routes.

(14) Order 8260.58, United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design.

b. Other Documents.

(1) ARINC Specification 424, Navigation System Data Base.

(2) IACC No. 4, Interagency Air Cartographic Committee Chart Specification for Low Altitude Instrument Approach Procedures.

(3) IACC No. 7, Interagency Air Cartographic Committee Chart Specification for Standard Instrument Departure Charts.

(4) IACC No. 17, Interagency Air Cartographic Committee Chart Specification for Terminal Procedures Publications.

(5) RTCA DO-187, Minimum Operational Performance Standards for Airborne Area Navigation Equipment Using Multi-Sensor Inputs.

5. Forms and Reports. Appendices B, C, D, E, F, and G contain requirements data, applicable forms, and associated instructions.

6. Information Update. For your convenience, FAA Form 1320-19, Directive Feedback Information, is included at the end of this order to note any deficiencies found, clarifications needed, or suggested improvements regarding the contents of this order. When forwarding your comments to the originating office for consideration, please provide a complete explanation of why the suggested change is necessary.

05/30/2014 8260.46E Appendix A

THIS PAGE IS INTENTIONALLY LEFT BLANK

6. Line 6. Route. › d. Line 6.4. Fix(es). Enter each fix in the order flown. For the…

05/30/2014 8260.46E 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 chapter 3. 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. 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 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.

d. Line 6.4. Fix(es). Enter each fix in the order flown. For the Departure IF, either indicate a specific point or at least describe the factors constraining the placement of the fix. Enter

11. Line 11. Remarks. › b. Enter appropriate information to clarify a data entry; e.g.,…

05/30/2014 8260.46E Appendix B

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 reestablished in a proposed Air Traffic environment order.

b. Enter appropriate information to clarify a data entry; e.g., airspeed restriction for air traffic, maximum altitude for aircraft performance, etc.

Appendix B. › 12. Line 12. Point of Contact (POC). Self-explanatory.

05/30/2014 8260.46E Appendix B

c. If the proposed DP does not meet the criteria requirements in chapter 2, paragraph 2-1-1, 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.

05/30/2014 8260.46E Appendix B

THIS PAGE INTENTIONALLY LEFT BLANK

05/30/2014 8260.46E 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: …

05/30/2014 8260.46E 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 … 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: …

05/30/2014 8260.46E 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: ATC Facility Name. POC’s Name. Telephone Number. Fax Number. E-Mail Address.

05/30/2014 8260.46E Appendix B

THIS PAGE INTENTIONALLY LEFT BLANK

Appendix C. Instructions for Completing FAA Form 8260-2, Data Worksheet › 13. Block 11. Point-of-Contact (POC). Self explanatory.

05/30/2014 8260.46E Appendix C

Appendix C. Instructions for Completing FAA Form 8260-2, Data Worksheet

Instructions for completing 8260-2, Data Worksheet, (see figure C-1) for requesting modification of fixes (including “Fix Use” updates) and/or holding patterns associated with existing 14 CFR Part 95 routes, 14 CFR Part 97 approaches, Special instrument procedures, SID or STARs. Complete this worksheet with as much information as possible and explain the addition or deletion in Block 10, Remarks. Submit this worksheet to the Office of Primary Responsibility (OPR) identified on the Form 8260-2 for proper action to be taken. For those fixes/holding patterns documented on older versions of Form 8260-2 that do not contain an OPR listed, contact the National Flight Data Center (NFDC), for a determination on where to submit this request. Block 1. Requested Publication Date. Enter the desired effective date that coincides with the charting cycle (see Order 8260.26, appendix A). If the Form 8260-2 request is to be in conjunction with an airspace action, obtain the docket number from the Western, Central, or Eastern Service Area for En Route Operations, Airspace Group.

For Form 8260-2 requests, allow at least 20 weeks lead-time from the desired effective date. Block 2. Fix Name. Enter the 5-character pronounceable name obtained from ARTCC. Do not include “WP” as part of the name. If requesting holding at a navigational aid, enter the name and type of navigational aid. Block 3. Fix Type. List the type(s) of fix, e.g., RADAR, WP, DME, INT (made up of crossing radials, bearings, or combinations of both). Block 4. STATE. Enter the state in which the fix is located. Block 5. ICAO Region Code. Enter the ICAO Region code in which the fix is located. Block 6. Location. Latitude and longitude accurate to the hundredth of a second; e.g., 09.25 sec. List all navigational aids used for the fix makeup. Provide radials or bearings, DME, and distance values to the hundredth value; e.g., 347.23°; 08.37NM. Block 7. Type of Action Required. Check applicable box to establish, modify, or cancel the fix. If there is no change to the fix, check “no change. Block 8. Holding. Describe holding patterns required at fix.

When climb-in-holding is required, provide detailed holding instructions including maximum altitude and maximum speed (if other than standard). Block 9. Charting. Indicate required charting; i.e., terminal, SIDs, STARs, or en route charts. Block 10. Remarks. List all procedures which use the fix and other uses of the fix; e.g., reporting points, etc. Include any other information that may assist in developing the fix. Justify the requirement for other than routine processing and charting. 13. Block 11. Point-of-Contact (POC). Self explanatory.

05/30/2014 8260.46E Appendix C

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

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

6. Takeoff Minimums. › b. List the runway(s) authorized standard takeoff minimums.

05/30/2014 8260.46E 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 2-1-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 (MagVar) rotation. If the procedure is a “Special,” the Regional Flight Standards Division, NextGen Branch (RNGB), will enter the effective date.

5. AMDT No. Enter standard entry as on Standard Instrument Approach Procedures (SIAP).

6. 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 2-1-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 9, 31: Standard. Followed by:

Continue reading ↓ 120 of 235 passages shown