Order 8260.46H Departure Procedure (DP) Program
This order provides policy, guidance, and standardization for initiating, developing, processing, and managing the DP program. This order contains guidance that is pertinent to Title 14, Code of Federal Regulations, (14 CFR) parts 71, 91, 97, 121, and 135.
This document is cancelled. Cancelled by 8260.46J. Check the official source before relying on it.
Text read by OCR from a scanned file (46 of 146 pages). Check the original, as some words may be misread.
FAA Order 8260.46H
Distribution: Electronic Distribution Initiated By: AFS-400
ORDER 8260.46H
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.
Effective Date:
06/04/2021
National Policy
SUBJ: Departure Procedure (DP) Program
FAA Order 8260.46H › Table of Contents
i
Table of Contents
Chapter 1. General Information … 1-1
Section 1-1. Basic … 1-1
1-1-1. Purpose of this order … 1-1 1-1-2. Audience … 1-1 1-1-3. Where you can find this order … 1-1 1-1-4. What this order cancels … 1-1 1-1-5. Explanation of changes … 1-1
Chapter 2. Responsibilities … 2-1
Section 2-1 … 2-1
2-1-1. Departure Procedure (DP) Guidelines … 2-1 2-1-2. Responsibilities … 2-22 2-1-3. Accuracy Verification and Responsibilities … 2-26 2-1-4. Military Departure Procedures … 2-26 2-1-5. FAA 8260-15 Series Forms … 2-27 2-1-6. Procedure Amendments … 2-28
Chapter 3. Guidelines for the Design of Graphic Instrument DPs … 3-1
Section 3-1 … 3-1
3-1-1. General … 3-1 3-1-2. Graphic ODPs and SIDs must include a minimum safe altitude (MSA) … 3-2 3-1-3. Naming of DPs … 3-2 3-1-4. Transition Naming … 3-3 3-1-5. Computer Identification Codes … 3-3 3-1-6. RNAV DPs … 3-4 3-1-7. Examples of Various Graphic Departure Scenarios … 3-6
Appendix A … A-1
1. Distribution … A-1 2. Background … A-1 3. Definitions … A-1 4. Acronym List … A-4 5. Related Publications … A-6 6. Forms and Reports … A-7 7. Information Update … A-7
Appendix B … B-1
1. Line 1 – Airport ID(s) … B-1 2. Line 2 – City and State … B-1 3. Line 3 – DP Name and Computer Codes … B-1 4. Line 4 – Action Required … B-1 5. Line 5 – Communications … B-1 6. Line 6 – Route … B-1
ii
7. Line 7 – Transitions … B-2 8. Line 8 – Lost Communications … B-2 9. Line 9 – Graphic Depiction … B-2 10. Line 10 - Requested Publication Date or Airspace Docket Number … B-2 11. Line 11 - Remarks … B-2 12. Line 12 - Point of Contact … B-3
Appendix C … C-1
Appendix D … D-1
Section 1. Instructions for Completing FAA Form 8260-15A … D-1
1. Develop a separate Form 8260-15A for each airport … D-1 2. Airport Identifier … D-1 3. City and State … D-1 4. AMDT No … D-1 5. Actual Effective Date … D-1 6. Takeoff Minimums … D-1 7. TEXTUAL Departure Procedure … D-2 8. Visual Climb Over Airport … D-4 9. Takeoff Obstacle Notes … D-4 10. Controlling Obstacles … D-5 11. Remarks … D-6 12. Flight Inspected By … D-6 13. Developed By … D-6 14. Approved By … D-6 15. Required Effective Date … D-6 16. Coordinated With … D-6 17. Changes/Reasons … D-6
Section 2. Instructions for Completing FAA Form 8260-15B (non-RNAV DPs) … D-12
1. Title Line … D-12 2. Type … D-12 3. DP Route Description … D-12 4. Transition Routes … D-13 5. PBN Requirement Notes … D-14 6. Equipment Requirement Notes … D-14 7. Procedural Data Notes … D-14 8. Takeoff Minimums … D-14 9. Takeoff Obstacle Notes … D-15 10. Controlling Obstacles … D-15 11. Lost Communications Procedures … D-16 12. Additional Flight Data … D-16 13. Airports Served … D-17 14. Communications … D-17 15. Fixes and/or NAVAIDs … D-17 16. MSA … D-18 17. Remarks … D-18
iii
18. Flight Inspected By … D-18 19. Developed By … D-18 20. Approved By … D-18 21. Required Effective Date … D-18 22. Coordinated With … D-19 23. Changes/Reasons … D-19
Appendix E … E-1
Section 1. Instructions for Completing FAA Form 8260-15B (RNAV DPs) … E-1
1. Title Line … E-1 2. Type … E-1 3. DP Route Description … E-1 4. Transition Routes … E-4 5. PBN Requirement Notes … E-5 6. Equipment Requirement Notes … E-5 7. Procedural Data Notes … E-5 8. Takeoff Minimums … E-5 9. Takeoff Obstacle Notes … E-6 10. Controlling Obstacles … E-7 11. Lost Communications Procedures … E-8 12. Additional Flight Data … E-8 13. Airports Served … E-9 14. Communications … E-9 15. Fixes and/or NAVAIDs … E-9 16. MSA … E-10 17. Remarks … E-10 18. Flight Inspected By … E-10 19. Developed By … E-10 20. Approved By … E-10 21. Required Effective Date … E-10 22. Coordinated With … E-11 23. Changes - Reasons … E-11
Section 2. Instructions for Completing FAA Form 8260-15C … E-27
1. Basic instructions for completing Form 8260-15C … E-27 2. Departure Routing to DP Fix … E-27 3. For each authorized runway … E-28 4. Transition Routing … E-29
Section 3. Instructions for Completing FAA Form 8260-15E (RNAV DPs) … E-40
1. General … E-40 2. Title Line … E-40 3. General Information … E-40 4. Additional Airport Information … E-41 5. Administrative Information … E-41 6. AAUP Processing … E-42
iv
Appendix F. Helicopter RNAV Departure Procedures … F-1
1. General … F-1 2. Departure Procedure … F-1 3. Documentation … F-1
Appendix G … G-1
1. Documentation … G-1
b. Chapter 2. › (1) Defined charting communications requirement.
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. This order contains guidance that is pertinent to Title 14, Code of Federal Regulations, (14 CFR) parts 71, 91, 97, 121, and 135.
1-1-2. Audience. All personnel who are responsible for instrument flight procedure development.
1-1-3. Where you can find this order. You can find this order on FAA’s website.
1-1-4. What this order cancels. Order 8260.46G, Departure Procedure (DP) Program, dated 11/09/2018.
1-1-5. Explanation of changes. Significant areas of new direction, guidance, policy, and criteria as follows:
a. General.
(1) Removed all references to All Weather Operations (AWO) and replaced with Flight Procedure and Airspace Group’s designated representative.
(2) Removed all references to Flight Procedure Implementation and Oversight and replaced with Flight Procedures and Airspace Group.
(3) Removed all references to Performance Based Flight Systems Branch and replaced with Flight Operations Group.
(4) Removed all references to Aeronautical Information Services National Flight Data Center (NFDC) and replaced with AJV-A Aeronautical Data Group.
(5) Removed all references to AJV-54 and replaced with AJV-A.
(6) Removed all references to AJV-54 NFDC and replaced with Aeronautical Data Group (AJV-A31).
(7) Removed all references to Flight Inspection Services and replaced with Flight Program Operations.
(8) Added new language for procedure developers to be FAA Service Providers or Non-FAA Service Providers.
b. Chapter 2.
(1) Defined charting communications requirement.
1-1-5. Explanation of changes. › f. Appendix F, Section 1. Removed requirement for a Form 8260-15A if…
(2) Added a third top altitude “assigned by ATC.”
(3) Clarified equipment notes and NavSpec requirements.
(4) Removed reference NAVAID requirement.
(5) Removed reference to Army and Form 8260-15.
(6) Removed RVR baseline requirement of 250 feet apart. RVR transmissometers no longer exist with this requirement.
c. Chapter 3. Added MSA guidance for ODPs and SIDs.
d. Appendix D, Section 2.
(1) Added MSA requirement and documentation.
(2) Replaced all Form 8260-15A samples with revised ones (Airport field removed).
e. Appendix E. Section 1. Added MSA requirement.
f. Appendix F, Section 1. Removed requirement for a Form 8260-15A if only used to name the departure for special helicopter procedures.
b. Obstacle departure procedures. Develop an ODP and/or non-standard… › (2) Establish only one ODP for a runway.
Chapter 2. Responsibilities
Section 2-1.
2-1-1. Departure Procedure (DP) Guidelines.
a. General. Instrument flight rules (IFR) departure procedures may be designed and published for all runways authorized by the approving authority. There are two types of DPs; those developed to assist pilots in obstruction avoidance (referred to as ODP) and those developed to communicate air traffic control (ATC) clearances (referred to as SID). Helicopter point-in-space (PinS) departures may be developed and charted as a SID (see Appendix F).
(1) Where IFR departure procedures are authorized by the approving authority conduct a diverse departure assessment for those airports with approved instrument approach procedures. ODPs are developed by FAA Service Providers at locations where they have instrument procedure development responsibility. Do not conduct a diverse departure assessment for helicopter departures. IFR diverse departures are not authorized, visual or VFR departure to an IDF may be authorized. (see Order 8260.42, U.S. Standard for Helicopter Area Navigation).
(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 Service Providers to ensure a terminal instrument procedures (TERPS) diverse departure obstacle assessment is accomplished and an ODP developed, where applicable.
(3) When IFR departure procedures are not authorized identify runway/heliport and reason on Form 8260.15A (see Appendix D, Section 1, paragraph 7).
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). Use Table 2-1-1 as a guide to determine each situation and the required action. Use Figure 2-1-1, Figure 2-1-2, or Figure 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 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.”
b. Obstacle departure procedures. Develop an ODP and/or non-standard… › (10) When applicable, develop ODPs using ground based NAVAIDs, RNAV, or…
(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) 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 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 the FAA Service Provider. When determining the need for a graphic DP, the FAA Service Provider must, in addition to the textual DP restrictions noted in paragraph 2-1-1.b(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, and
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 and/or RNAV LNAV engagement; 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 paragraph 3-1-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, RNAV, or dead reckoning guidance wherever possible. Do not specify radar vectors for navigation guidance in
b. Obstacle departure procedures. Develop an ODP and/or non-standard… › (16) Helicopter PinS departures are published only as a SID.
ODP development. At those locations served by RNAV approaches exclusively, every effort must first be made to develop an ODP that accommodates conventional (preferably very high frequency omni-directional range (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 9).
(12) Do not establish a VCOA maneuver in conjunction with an RNAV ODP.
(13) The VCOA requirement in Table 2-1-1 is mandatory. However, ATC may submit a justification request to the Flight Procedures and Airspace Group for 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 and at the appropriate altitude for route of flight.
(16) Helicopter PinS departures are published only as a SID. ODPs are not required (see Appendix F).
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 statute miles (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 ICA (extended) 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.
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.
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 ICA (extended) 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 VCOA to an altitude that will provide obstacle clearance (see paragraph 2-1-1.b(11), 2-1- 1.b(12), and 2-1-1.b(13)), or
3) A combination of options 1 and 2 above.
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.
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
i. Provide a ceiling and visibility to see and avoid the ≤ 3 SM obstacle and the minimum CG required to clear all other
Situation Action obstacles outside the ICA (extended) to a specified fix or altitude that provides obstacle clearance, and
ii. For ICA (extended) 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
iii. Provide a ceiling and visibility sufficient to allow a VCOA to an altitude that will provide obstacle clearance (see paragraphs 2-1-1b.(11), 2-1-1.b(12), and 2- 1-1.b(13)),
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.
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.
D) If none of the above actions is 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 feet 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: “NOTE: RWY 23: (ENTER OBSTACLE NOTES).”
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 ft per NM climb gradient, takeoff must occur no later than 1600 feet 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: “NOTE: RWY 23: (ENTER OBSTACLE NOTES).”
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 ft per NM to 5000 or 2100-3 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)” 3. TAKEOFF MINIMUMS: “RWY 5: Standard with minimum climb of 425 ft per NM to 5400 or 2100-3 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)” 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 feet 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 feet 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: “NOTE: RWY 23: (ENTER OBSTACLE NOTES).”
d. Design constraints. The following design constraints apply to all… › (3) Specify speed restrictions only when necessary to ensure obstacle…
c. Standard instrument departures. Develop SIDs to assist in meeting environmental, capacity, and ATC requirements. SIDs may be requested by specific ATC facilities, the military services, or other proponents to enhance operations. A SID also provides protection from obstacles and is depicted graphically; however, it will not contain the “(OBSTACLE)” designation following the procedure title on the chart, and may not be flown unless approved by ATC. The following rules apply to SIDs:
(1) 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 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 DER.
(2) The Flight Procedures and Airspace Group (or appropriate military authority) must approve DPs and DVAs requiring a CG in excess of 500 ft/NM (600 ft/NM for helicopters). See paragraph 2-1-1.e(3) for additional information regarding establishing/publishing greater than standard climb gradients.
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 the Flight Procedures and Airspace Group 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) three 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 the Flight Procedures and Airspace Group 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 three 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.
(2) Charting altitudes. Document altitudes for charting as follows: › (b) When ATC requests a minimum “at or above” altitude restriction at a…
(a) Speed restrictions to support ATC requirements are only allowed in SID design and must not be included in ODPs.
(b) Limit speed restrictions to one restriction per fix/waypoint. In this instance, an altitude that meets TERPS criteria (or if applicable, a higher altitude for ATC operational requirements) must also be charted at the fix/waypoint.
(c) Speed restrictions may apply to the entire procedure or to a specific point-inspace. Use standard notes, where possible, so that the intent can be clearly understood by the pilot; e.g., “DO NOT EXCEED XXX KIAS UNTIL PASSING (FIX NAME);” “DO NOT EXCEED XXX KIAS UNTIL LEAVING (ALTITUDE);” “INCREASE SPEED TO XXX KIAS, IF UNABLE, ADVISE ATC.”
(d) For the portion of a DP that underlies Class B airspace, do not chart minimum or mandatory speed restrictions in excess of 200 KIAS. Do not establish speed restrictions that require an aircraft to exceed the restrictions in 14 CFR part 91.117 (a) and (c).
(e) Do not chart minimum or mandatory speed restrictions in excess of 250 KIAS below 10,000 feet MSL.
(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 departure route from the end of a runway to the end of the DP to support different types of aircraft (e.g., 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) Communications. Charting of the Departure Control frequency will occur automatically (without coordination). Other communication types will be depicted only when specifically requested. For additional frequencies requested by the Instrument Flight Procedure Validation Team or specified on the worksheet, specify Chart ATIS, Chart CLNC DEL, etc.
(2) 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
(2) Charting altitudes. Document altitudes for charting as follows: › (f) For SIDs, enter the Top Altitude(s) on Form 8260-15B, Graphic…
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)).
1. When establishing crossing altitudes for other than meeting obstacle clearance and/or to support a shortened ICA to ensure RNAV LNAV engagement can occur before turning, 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 industry partners and local operators that could be impacted.
2. Calculate (but do not publish) the CG necessary to meet each minimum altitude restriction. Flight Procedures and Airspace Group’s approval is required if the calculated CG exceeds 500 ft/NM (600 ft/NM for helicopters).
(c) When an ATC facility has requested an “at or below” altitude restriction at a fix, ensure that the requested altitude meets all required obstacle clearance (ROC) requirements specified in Order 8260.3, Chapter 14, 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 paragraph 2- 1-1.e(2)(b)).
(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-1.e(2)(b)). Do not raise an MEA to support ATC operational requirements; use fix crossing altitudes where operationally needed.
(e) Enter altitudes to be charted on the appropriate 8260-15 series form (see Appendix D or Appendix E). Government and civil charting organizations will chart/depict these altitudes according to their individual specifications.
(f) For SIDs, enter the Top Altitude(s) on Form 8260-15B, Graphic Departure Procedure. Top Altitudes will be provided by the applicable controlling ATC Facility, the Service Area Flight Procedures Team (FPT), or be specified within the Graphic Departure Procedure Requirements Worksheet per Appendix B, etc.). A top altitude may be a specific altitude, a specific flight level, or may be in the form of, “Assigned by ATC.” A maximum of two numerical values Top Altitudes are allowed per SID (see Note below). A third Top Altitude in the form of “assigned by ATC” may be used when flexibility is needed for the efficient flow of traffic. The variations permitted are specified in Appendix D, Section 2, and Appendix E, Section 1. Top Altitudes 18,000 feet MSL and above must be specified as a Flight Level. The Top Altitude provided must be at or above all fix crossing altitude restrictions specified along the departure route and transitions and must not be lower than the highest climb to altitude listed in the takeoff requirements of the procedure. For example, if the Takeoff minimums state a 360 ft/NM climb gradient until reaching 6000, the ATC assigned Top Altitude will be no lower than 6000.
(4) Charting speed restrictions. › (b) Annotate speed restrictions for graphic ODPs and SIDs on the chart…
Note: Even though a SID may serve more than one airport, a maximum of only two numerical values and one “assigned by ATC” per SID are authorized. Top Altitudes may be specified on each Form 8260-15B.
(3) Charting a minimum CG. 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, Appendix E, or Appendix F).
(a) 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 PER NM TO 4300.”
(b) When a CG is necessary to support a shortened ICA to ensure RNAV LNAV engagement occurs before turning (e.g., 500 ft/NM to 1300), a reduced, second CG may be established in this situation only (i.e., a maximum of two CGs).
(c) Do not chart CGs that may be needed to support airspace, navigation solution, environmental, or ATC operational limitations.
Note 1: Pilots are expected to determine if minimum crossing altitudes can be met, based on the performance capability of the aircraft they are operating. However, CGs must be evaluated between fixes where minimum crossing altitudes have been established to determine if the CG is excessive/unrealistic for the anticipated types of aircraft that will use the SID. These CGs will not be charted. See paragraph 2-1-1.e(2)(b) for action that may be necessary.
Note 2: Helicopter point-in-space IFR departures depart VFR (or may depart visually for approved Special) 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.
(4) Charting speed restrictions. Identify required speed restrictions per Interagency Air Committee (IAC) specifications. Also, see paragraph 2-1-1.d(3) for design constraints.
(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.”
f. Equipment requirements. DPs are also categorized by equipment… › (2) RNAV DP.
(5) ODPs depicted graphically must have the term “(OBSTACLE)” printed on the graphic (see Appendix D or Appendix E). Indicate the word “OBSTACLE” adjacent to the “Type” line on Form 8260-15B. U.S. Government charts will include this immediately following the procedure title; e.g., TETON ONE DEPARTURE (OBSTACLE).
(6) 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).
(7) All Graphic DPs must include applicable takeoff minimums and climb gradients on the graphic chart. Obstacle DPs must also include obstacle data (see Table 2-1-1) on the graphic chart, even if redundant to information published textually.
(8) ATC radar vectoring may be used as part of an RNAV SID and 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).
(9) When ATC has determined that they do not want pilots to “Flight Plan” or file a particular SID (i.e., use will be determined by ATC), ATC will request that a chart note be placed on the SID. In the “Procedural Data Notes” section of Form 8260-15B, use: “CHART NOTE: DO NOT FILE – TO BE ASSIGNED BY ATC.”
(10) A navigation specification (NavSpec) contains the performance-based accuracy integrity, and continuity requirements of PBN navigation for a given airspace construction. Apply the RNAV 1 NavSpec for PBN departures under most circumstances. Alternative use of RNP 1, A-RNP, or RNP AR DP NavSpecs is detailed in Order 8260.58. For the en route phase of flight, including SID en route transitions, the standard NavSpec is RNAV 2. The lateral navigation accuracy value of one or two indicates, in miles, the distance from the centerline of the flightpath that must be maintained for aircraft and obstacle separation.
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.
Note: Do not combine non-RNAV and RNAV SIDs on the same chart. However, RNAV waypoints may be depicted on conventional Radar SID charts to support ATC operational requirements.
(6) RNAV chart annotation › (c) Specify PBN requirements notes on Form 8260-15B in the following…
(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.
(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-1.f(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) RNAV chart annotation: A navigation specification (NavSpec) contains the performance-based accuracy integrity, and continuity requirements of PBN navigation for a given airspace construction. Apply the RNAV 1 NavSpec for PBN SIDs under most circumstances. Alternative use of RNP 1, A-RNP, RNP AR DP NavSpecs is detailed in Order 8260.58. For the en route phase of flight, including SID en route transitions, the standard NavSpec is RNAV 2.
(a) Provide a PBN Requirements Box when there is a PBN segment in the procedure.
(b) Separate the PBN Requirements Box from other procedural and nonprocedural notes and information on the chart
(c) Specify PBN requirements notes on Form 8260-15B in the following format: “NavSpec – Sensor, Function. Remarks.” When the note does not contain Function and Remark, the “period” is placed after the Sensor (e.g. “RNP 1 - GPS.”). When the note does contain a Remark, the “period”, in the Remark, is placed after the NavSpec or Sensor or Function and Remark (e.g., “RNAV 1 – GPS. FROM YABUT: RNP 1.” or “RNP 1 - GPS. FROM YABUT: A-RNP, MIN RNP 0.30. AP/FD.”).
1. NavSpec: The NavSpecs are defined in Order 8260.58 as RNAV 1, RNP 1, A-RNP, and RNP AR DP (see Appendix E). When a NavSpec is only applicable to a specific runway transition(s) or leg(s) of a DP, identify this is a “Remark” by stating the waypoint where the NavSpec begins followed by NavSpec - Sensor, Function. Remark (e.g. “RNAV 1 – DME/DME/IRU or GPS. FROM YABUT: RNP 1 - GPS, RF.”).
2. Sensor: The required sensor is applicable to the NavSpec.
a RNAV 1: DME screening must be assessed. If DME screening results are satisfactory and radar monitoring is provided authorize DME navigation and the sensor is DME/DME/IRU OR GPS. If result is not satisfactory or monitoring is not provided, the sensor is GPS.
b RNP 1 , A-RNP, and RNP AR DP: The only authorized sensor is GPS. No ATC monitoring is required on RNP routes (do not annotate “RADAR REQUIRED”).
3. Function: Common functions are RF turns and MIN RNP scalable values. They can be applicable to the entire DP or only to a specific runway transition(s) or leg(s).
a RF turns applicable to all runway transition(s) or leg(s) of the DP: Identify this as the function (e.g., “RNP 1 – GPS, RF.”).
b RF turn applicable only to a specific runway transition(s) or leg(s) of a DP: Identify this as a “Remark” by stating the waypoint where the RF turn begins followed by NavSpec - Sensor, Function. Remark. (e.g., “RNAV 1 – DME/DME/IRU or GPS. FROM YABUT: A-RNP - GPS, MIN RNP 0.30. AP/FD.”).
c Lateral Accuracy Function: A-RNP has scalable lateral accuracy values of 1.00 or 0.30. RNP AR DP has lateral accuracy scalable values from 1.00 to 0.30. Document only A-RNP or RNP AR DP NavSpecs when the lateral accuracy value is < 1.00. (e.g., “A-RNP - GPS, MIN RNP 0.30 AP/FD.” or “RNP AR DP – GPS, MIN RNP 0.70, AUTHORIZATION REQUIRED”).
4. Remark: Common remarks are Autopilot/Flight Director (AP/FD) and Authorization Required. Additionally when a NavSpec, Sensor or Function is only applicable to a specific runway transition(s) or leg(s) document this as a remark.
a A-RNP require AP/FD; document AP/FD as a remark.
b RNP AR DP require authorization; document “AUTHORIZATION REQUIRED” as a remark.
c When the NavSpec does not change but a Function (RF/Lateral Accuracy value <1.00) is only applicable to a specific runway transition(s) or leg(s) then do not repeat the NavSpec (e.g., “RNP 1 – GPS. FROM YABUT: RF.” or “A-RNP – GPS. AP/FD. FROM HEERE: RF, MIN RNP 0.30.”).
d When the NavSpec does not change but a Remark (AP/FD or AUTHORIZATION REQUIRED) is only applicable to a specific runway transition(s) or leg(s) then do not repeat the NavSpec (e.g., “A–RNP – GPS. AP/FD. FROM YABUT: RF, MIN RNP 0.30.”).
e When the Sensor does not change but a NavSpec, Function, or Remark is only applicable to a specific runway transition(s) or leg(s) then do not repeat the Sensor (e.g., “RNP 1 – GPS. FROM YABUT: A–RNP, RF.”).
f When more than two waypoints are listed use a comma between waypoints and “OR” prior to the last waypoint (e.g. “FROM YABUT, HEERE OR THERE: RF.”
5. Common PBN requirements notes(s) as applicable:
g. Terminology. The following terminology applies for initial climb… › (2) If departure instructions require ATC to assign a heading or…
a RNAV 1 (no RF turns or NavSpec for a specific runway transition(s)/leg(s): “RNAV 1 – GPS.” or “RNAV 1 – DME/DME/IRU OR GPS.”).
b RNAV 1 (with specific RF turns): “RNAV 1 – DME/DME/IRU OR GPS. FROM HEERE OR THERE: RNP 1 – GPS, RF.”
c RNP 1 (no RF turns): “RNP 1 – GPS.”
d RNP 1 (with RF turns or specific RF turns): “RNP 1 – GPS, RF.” or “RNP 1 – GPS. FROM HEERE OR THERE: RF.”
e A–RNP (lateral accuracy of 1.00 and no RF turns): “A-RNP – GPS, AP/FD.”
f A–RNP (lateral accuracy of 0.30 and no RF turns): “A-RNP – GPS, MIN RNP 0.30, AP/FD.”
g A-RNP (lateral accuracy of 0.30 and specific RF turns): “A-RNP – GPS, RF MIN RNP 0.30, AP/FD” or “A-RNP – GPS. AP/FD. FROM HEERE OR THERE: RF, MIN RNP 0.30.”
h RNP AR DP (lateral accuracy of 1.00 and no RF turns): “RNP AR DP – GPS, AUTHORIZATION REQUIRED.”
i RNP AR DP (lateral accuracy < 1.00 and no RF turns): “RNP AR DP – GPS, MIN RNP 0.70. AUTHORIZATION REQUIRED.”
j RNP AR DP (lateral accuracy < 1.00 and specific RF turns): “RNP AR DP – GPS, RF, MIN RNP 0.50. AUTHORIZATION REQUIRED.” or “RNP AR DP – GPS. AUTHORIZATION REQUIRED. FROM HEERE OR THERE: RF, MIN RNP 0.70.”
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 on 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 or heading and altitude, use “Climb on assigned heading for radar vectors to (name of fix/airway, etc.),” or “Climb on assigned heading to (altitude) 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 on heading 310.25 to 1500 …”
(1) Site Implementation Team (SIT). › (a) Comprised of FAA and industry members with the team leadership…
(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 on heading 240.15 to1500, cross TEB 4.5 DME at 1500, then climb and maintain 2000, thence…” or, “Climb on heading 195.47 to 1500, then climbing right turn to heading 280, maintain 4000, thence…” or “Climb on heading 123.31 to 3000, then climbing left turn to assigned heading for Radar vectors to HAIKU, maintain 14,000, 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 the Flight Standards Service 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 (AAUP). 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 14c.
(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 to 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.
2-1-2. Responsibilities. › a. General. The following guidance outlines procedures for DP requests,…
(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, Attention All Users Page, 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 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) must submit the draft AAUP to [email protected]. For departure AAUPs, include documentation of coordination with Air Traffic Mission Support Services, Mission Support Policy Directorate (AJV-P). Use the subject line “Approval Request: AAUP Simultaneous Arrival” or “Approval Request: AAUP Simultaneous RNAV DP” as appropriate. Flight Operations Group will submit the approved AAUP and requested effective date to Aeronautical Information Services.
EXCEPTION: In the case of a Special Procedure requiring an AAUP, Flight Procedures and Airspace Group will coordinate the effective date with the appropriate parties.
(4) AAUP publication. The originating organization will determine the required publication date; coordinate with Aeronautical Information Services as necessary. After receiving the AAUP from the Flight Operations Group, the Aeronautical Data Group will:
(a) Verify the applicability of the publication date and assign that date for publication.
(b) Coordinate with the Flight Operations Group who will, in turn, contact the originating organization and Aeronautical Information Services 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, Aeronautical Information Services Instrument Flight Procedures Group, Aeronautical Information Services, Aeronautical Data Group, and the Flight Operations Group 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.
c. ATC. When assisting a proponent or requesting a SID, the ATC… › (2) Assist in designing the procedure by providing the proponent with…
(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 through the Aeronautical Information Services “IFP Gateway.” Process all requests for new or amended SIDs through the Service Area Operations Support Group, Flight Procedures Team (OSG FPT) and the OSG FPT will forward to the appropriate Instrument Flight Procedure (IFP) Validation Team 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. Aeronautical Information Services 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, Aeronautical Information Services, Flight Procedures and Airspace Group, and other ATO organizations/involved parties must work together to find an acceptable solution.
(3) Cancellation. The IFP Validation Team must approve all proposed SID cancellations. AJV-A has sole responsibility for canceling ODPs. AJV-A 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 Appendix B and Appendix 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 ATO is responsible for satisfying the requirements for 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.
d. Service Area Operations Support Group. › (4) Ensure that a DME/DME screening model has been run on RNAV SIDs to…
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 five-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.
(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 OSG. 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 Appendix E).
(8) Review SIDs at least biennially for continued need. Coordinate requested changes through the applicable Service Area OSG FPT.
(9) Collaborate with the Flight Operations Group when the development of an AAUP is necessary for RNAV departure procedures. See paragraph 2-1-1.i for additional guidance.
d. Service Area Operations Support Group.
(1) Review the DP package for completeness.
(2) Review DPs for impact based on Facilities and Equipment changes, National Change Proposal, 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 Flight Procedure and Airspace Group’s designated representative 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.
e. Aeronautical Information Services. › (9) Assign an effective date for all ODPs, SIDs, and DVAs.
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 IFP Validation Team.
(6) Forward the DP package to AJV-A.
(7) Provide one copy of each 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.
(9) The OSG FPT must ensure that changes to the NAS comply with Order 1100.161, paragraph 3-2.
e. Aeronautical Information Services.
(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.
(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 Program Operations, for necessary action.
(7) After satisfactory flight inspection, forward the original Form(s) 8260-2 and original 8260-15 series forms to Aeronautical Data Team (AJV-A31). Copies are available for distribution (see paragraph 2-1-2.d(5)).
(8) Develop, review, track, and cancel Notices to Airmen (NOTAMs) relating to ODPs, SIDs, and Diverse Vector Areas (DVAs).
(9) Assign an effective date for all ODPs, SIDs, and DVAs. 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 Aeronautical Data Group for incorporation into the NFDD.
f. Flight Program Operations. › (2) Provide flight inspection results and archived reports upon…
(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 DPs 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, or DVA 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.
(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-5.c.
(16) Add the “T” symbol to the IAP and SID charts whenever the Form 8260-15A contains any data entries on the Form other than the word “Standard.”
Note: The “T” symbol will not be placed on graphic ODPs.
(17) Delete the “T” symbol from the IAP and SID charts whenever the Form 8260-15A reflects no data entries on the form other than the word “Standard.” 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, Flight Procedures and Airspace).
f. Flight Program Operations.
(1) Coordinate and execute flight validation and flight inspection for FAA-developed procedures and under a reimbursable agreement with other IFP providers,
(2) Provide flight inspection results and archived reports upon request, and
2-1-4. Military Departure Procedures. › b. The FAA requires that all military DPs be coordinated with FAA ATC…
(3) Verify DME/DME coverage when applicable.
g. Aeronautical Data Group.
(1) Conduct a review of submitted forms to ensure compatibility with the National Airspace System Resources (NASR), 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-1.i(4) for more specific AAUP responsibilities.
(3) Resolve data conflicts, form discrepancies, etc., with Aeronautical Information Services.
(4) File and maintain the original signed copy of the forms.
2-1-3. Accuracy Verification and Responsibilities. Any ATC facility, military, proponent, charting agency, procedure user, concerned individual, organization, or office must:
a. Notify Aeronautical Information Services of published errors (including omissions) that affect safety of flight by the fastest means available. Aeronautical Information Services must take appropriate NOTAM action under Order 8260.19.
b. Notify Aeronautical Information Services whenever pre-publication errors are discovered in the TL. Aeronautical Information Services will coordinate necessary corrective actions and promulgate corrected data/forms.
c. Notify the Aeronautical Data Group whenever pre-publication errors are discovered in the NFDD. The Aeronautical Data Group will coordinate necessary corrective actions and promulgate corrected data/forms.
d. Notify Aeronautical Information Services whenever charting discrepancies/compilation errors are detected in U.S. Government published aeronautical products. Aeronautical Information Services will coordinate corrective actions.
2-1-4. Military Departure Procedures.
a. 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 U.S. 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 when such DPs affect the NAS. The Air Traffic facility providing the departure service must assist the
(3) Use Form 8260-15C to document RNAV DPs in a manner consistent with… › (b) Altitude and airspeed restrictions associated with fixes.
military in coordinating the procedures and in obtaining computer codes to ensure that the procedures are properly interfaced with the NAS. U.S. Air Force and Navy procedures are NOT sent to Aeronautical Data Team (AJV-A31).
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 a military exception (see Order 8260.3 regarding departure criteria), the procedure must be annotated NOT FOR CIVIL USE.
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. For helicopter departures, see Appendix F.
(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 Form 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.
Section 2-1. › 2-1-6. Procedure Amendments.
(4) Use Form 8260-15D to document a DVA.
(5) Use Form 8260-15E to document RNAV DP AAUPs for locations where it has been determined that detailed departure information is necessary. See paragraph 2-1-1.i for AAUP guidance.
b. 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. See Order 8260.19, Chapter 2 for waiver and approval processing guidance.
c. Cancel the Form 8260-15(s) for specific takeoff minimums for an airport or cancel any textual or graphical DP(s) or DVA no longer required, as follows:
(1) Enter the current information from the top line of page 1 of Form 8260-15A/B/D and into the corresponding blocks on blank Forms 8260-15A and/or 8260-15B or 8260-15D. Additionally, on Form 8260-15B, complete the “Airports Served” section.
(2) Select “Cancellation” on the Form and “Procedure Canceled Effective (Date)” will automatically appear in the “Takeoff Minimums” section on Form 8260-15A and/or “DP Route Description” section of Form 8260-15B. For a DVA, select “Cancellation” above the “For ATC Use Only” box where this information will be entered automatically. A stamp may be used for this purpose. Do not enter a cancellation effective date for Special procedures.
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 Form 8260-15C, if an RNAV procedure) for processing (see Note 2). See Order JO 8200.44, Coordination of Flight Inspection Procedure Packages, for guidance on what must be submitted for flight inspection. Submit departure procedures developed by a non-FAA Service Provider to the Flight Procedures and Airspace Group to determine flight validation requirements.
Note 1: Flight Program Operations (or the Flight Procedures and Airspace Group 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 the Flight Procedures and Airspace Group a copy of all policy memorandums between Flight Program Operations 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.
(4) Use an abbreviated amendment whenever a change is made to the items… › (f) Airports served (only when an airport identifier, city/state has…
a. Textual ODPs.
(1) When completing a full amendment, advance the amendment number in the “AMDT No.” item of Form 8260-15A; e.g., “AMDT 1,” “AMDT 4.” When the “abbreviated amendment” process is used, an alphabetical suffix is added/advanced whenever the procedure is revised; for example “ORIG-A,” “AMDT 5C.” The circumstances dictating the need for revision determine whether an amendment or abbreviated amendment may be made or whether the existing procedure must be canceled and an original established.
(2) Use P-NOTAMs to act as an “abbreviated amendment” for Textual ODPs to effect changes immediately and to 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- 3.f)].
(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. See Appendix D, Section 2, and Appendix E, Section 1, for “Remarks” documentation requirements when an abbreviated amendment is used.
(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 an airport identifier, city/state has changed or an airport is deleted).
2-1-6. Procedure Amendments. › c. DVA. Any change to a DVA is considered an amendment and requires a…
(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 TARGETS assessment when altitude changes are made). This includes adding/revising Top Altitudes to a SID.
(k) Top altitude changes (adding/deleting/revising).
(l) 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.
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.
l. Altitude. › (2) Minimum and maximum block altitudes for the same fix/waypoint are…
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-1.d(3) and 2-1-1.e(4) 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-1.e(2) for specific guidance and charting constraints.
3-1-3. Naming of DPs (see Figure 3-1-1 through Figure 3-1-8). › b. SIDs designed using radar vectors as the only navigation source to…
(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.” See exception in paragraph 3-1-1.l(6).
(4) Define crossing altitude restrictions as “at-or-above,” or “at-or-below or “at.” Use of “at-or-above” altitudes are preferred; avoid “at” and “at-or-below” altitudes whenever possible.
Note: Do not use “Expect” altitude restrictions.
(5) Procedure designers must use good judgment and common sense, coupled with operational input where available, to restrict procedural altitudes due to precipitous terrain.
(6) For SIDs, procedure designers will be provided the Top Altitude(s) for documentation on Form 8260-15B. Top Altitudes must not exceed three per procedure, regardless of how many airports are served by the SID. See also paragraph 2-1-1.e(2)(f). Two top altitudes will be a numeric value; the third top altitude will be “as assigned by ATC.” This may be in the form of two different altitudes used to support different aircraft types (e.g., turbojet and propeller driven) since a Top Altitude is not coded as part of the departure procedure and will not appear on Form 8260-15C. ATC may elect to not publish a specific Top Altitude, preferring to issue the Top Altitude as part of the ATC clearance. When this occurs, ATC will request the Top Altitude information be stated as “Assigned by ATC,” and state “Maintain ATC Assigned Altitude” as part of Departure Route Description. See Appendix D, Section 2, or Appendix E, Section 1, for the Top Altitude variations permitted.
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 when needed to support a shortened ICA for RNAV LNAV engagement (see paragraphs 2-1-1.d(2) and 2-1-1.e(3) for specific guidance).
Note: Do not establish a greater than standard CG solely to reach an altitude sooner for RNAV LNAV engagement purposes when an early turn is not necessary. 3-1-2. Graphic ODPs and SIDs must include a MSA for each airport served by the DP. Establish an MSA for all graphic departure procedures within a 25-NM radius of a specified point for use during emergency situations.
3-1-3. Naming of DPs (see Figure 3-1-1 through Figure 3-1-8).
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.
3-1-5. Computer Identification Codes. See pages Appendix B for examples. › b. Graphic ODPs and SIDs. Computer identification codes are assigned to…
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 required navigation performance (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.
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-6.b for the amendment process).
3-1-4. 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-5. 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 three-letter NAVAID or airport identifier, a four-letter geographical abbreviation, or a five-letter fix/waypoint name, or other five-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-3.d is coded “CVG8.CVG”; the FORT LAUDERDALE SEVEN DEPARTURE in paragraph 3-1-4 is coded “FLL7.FLL” and the “TATES TWO DEPARTURE in paragraph 3-1- 3.d 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.
3-1-6. RNAV DPs. › b. Leg types. Table 3-1-1 shows permissible leg types for use with RNAV…
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-5.b, 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-4, the ZAPPA transition is coded “FLL7.ZAPPA.” Using the REDSS example in paragraph 3-1-4, the Johnstown transition is coded “REDSS4.JST.
3-1-6. 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.
b. Leg types. Table 3-1-1 shows permissible leg types for use with RNAV DPs.
Table 3-1-1. Permissible leg types
FROM VIA (leg type) TO AER CF3, DF4 FB/FO AER VI1 See 1 AER VA2 ALT AER VM8 HDG ALT CF3, DF4 FB/FO ALT VM2 ALT FO10 HM ALT FB TF5 FB/FO FB RF6 FB FO DF4, TF5 FB/FO FO VM8 HDG FO/FB FM9 Course IF7 DF4, TF5 FB/FO 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). The altitude must be an at-or-above altitude; a mandatory (i.e., “at”) altitude must not be used at the first fix. Do not use a VA leg specifically for engagement only.
3-1-6. RNAV DPs. › d. For RNAV chart annotation see paragraph 2-1-1.f(3).
3 CF may only be used as the first leg of a departure or as the leg following a departure VI leg. 4 DF 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. 8 VM 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 must be at an altitude at or above the minimum vectoring altitude or minimum IFR altitude for direction of flight. 10 HM legs are used when a climb in a holding pattern is required on departure to allow the aircraft to be at an altitude at or above the minimum vectoring altitude or minimum IFR altitude for direction of flight. See Figure E-7 and Figure E-13. Note: AER – approach end of runway; ALT – altitude; FB– fly-by fix; FO– fly-over fix.
(1) VA leg followed by DF leg – “Takeoff RWY 32R: Climb on heading 317.66 to 1000, then climbing right turn direct LARRY.”
(2) Although the first altitude of a VA/DF leg type sequence appears to be specified in the text instructions as a “mandatory” altitude, it must be documented on the Form 8260-15C as an “at or above” altitude to ensure all the various types of aircraft avionics equipment operate appropriately.
(3) VA leg followed by VM leg – “Takeoff RWY 32R: Climb on heading 317.66 to 1500, FOR VECTORS TO LARRY.”
Note: This leg type combination is used for “Radar Vectors to Join RNAV Routes” departure procedures where ATC wants the aircraft to climb on a specified heading to an altitude prior to initiating radar vectors. Following the vectoring sequence, ATC is expected to issue a clearance direct to the IDF.
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. For RNAV chart annotation see paragraph 2-1-1.f(3).
Section 3-1. › 3-1-7.
3-1-7. Examples of Various Graphic Departure Scenarios (see Figure 3-1-1 through Figure 3-1-8).
Figure 3-1-1. Graphic Departure Scenario #1, Obstacle DP with No Transitions
Figure 3-1-2. Graphic Departure Scenario #2, DP with No Transitions
Figure 3-1-3. Graphic Departure Scenario #3, DP with Two Transitions that Share a Common Segment
Figure 3-1-4. Graphic Departure Scenario #4, SID with Three Transitions
Figure 3-1-5. Graphic Departure Scenario #5, RNAV SID with Four Transitions
Figure 3-1-6. Graphic Departure Scenario #6, RNAV SID with Four Transitions
Figure 3-1-7. Graphic Departure Scenario #7, Radar Departure with Four Transitions
Figure 3-1-8. Graphic Departure Scenario #8, RNAV Departure Using Radar Vectors with Four Transitions
Appendix A › 3. Definitions.
Appendix A. Administrative Information
1. Distribution. This order is distributed electronically only.
2. Background. The original order combined into a single product, textual IFR departure procedures that were developed by the Aeronautical Information Services under the guidance of the Flight Standards Service, and graphic SIDs that were designed and produced under the direction of the 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 DP to facilitate pilot understanding of the procedure as well as all RNAV and 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” 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, “must” means 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. Aeronautical Data Group (AJV-A31). The FAA office responsible for the collection, validation, and dissemination of all aeronautical information relating to the NAS.
b. 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.
c. Area navigation (RNAV). A method of navigation which permits aircraft operations on any desired flight path within the coverage of ground- or space-based navigation aid or within the limits of the capability of self-contained aids, or a combination of these.
d. Climb gradient (CG). A climb requirement expressed in feet per NM (ft/NM).
e. Controller chart. An aeronautical chart developed for internal air traffic controller (ATC) reference in specific ATC facilities. These charts may also be used to design instrument procedures to support ATC operations.
f. Departure end of runway (DER). The end of the runway that is opposite the landing threshold.
g. 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 - ODPs printed either textually or graphically, and SIDs, which is always printed graphically.
h. Diverse vector area (DVA). An area in which a prescribed departure route is not required. Radar vectors may be issued below the minimum vectoring or minimum IFR altitude. It can be established for diverse departure, departure sectors, and/or video map radar areas portraying obstacles and terrain.
i. Electronic transmission. Transmittal via electronic mail (e-mail) or facsimile (fax).
j. 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.
k. Flight Procedures Team (FPT). An element of AJV, geographically located in each ATO Service Area.
l. Fly-by waypoint. A fly-by waypoint requires the use of turn anticipation to avoid overshoot of the next flight segment.
m. 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.
n. Initial climb area (ICA). A segment variable in length starting at the DER which allows the aircraft sufficient distance to reach an altitude of at least 400 feet above the DER.
o. 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 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.
p. Instrument Flight Procedure (IFP) Validation Team. A team located in each service center that will validate all IFP requests to ensure efficient use of FAA resources to benefit the National Airspace System (NAS).
q. Least onerous methods. The use of obstacle DP criteria standards to clear terrain or other obstacles that will result in the lowest possible climb gradient and/or route that provides the most efficient means for departing that runway.
r. National Flight Data Digest (NFDD). A daily publication, prepared by the Aeronautical Data Group (AJV-A31) to promulgate non-regulatory changes to the NAS.
s. Navigational aid (NAVAID) (see Aeronautical Information Manual). Any visual or electronics device airborne or on the surface which provides point-to-point guidance information or position data to aircraft in flight.
t. Non-RNAV DP. A DP whose ground track is based on ground-based NAVAIDs and/or dead reckoning navigation.
u. Obstacle. An object, structure, terrain feature, or vegetation, at a fixed geographical location, or which may be expected at a fixed location within a prescribed area, with reference to which vertical clearance must be provided during flight operations. Unless limited to certain heights, assume mobile objects 17-feet high are on Interstate Highways, mobile objects 15-feet high are on any other public roadway, mobile objects 10-feet high are on private roads, and mobile objects 23-feet high are on a railroad track. The tallest point of a watercraft (for example, the mast) is assumed according to the types of watercraft know to use an anchorage or to transit a waterway. Includes taxiing aircraft except where operational restrictions prevent taxi operations during takeoff and landings. Any mobile object may be ignored provided positive controls are applied by the airport authority or by air traffic control to exclude their presence during flight operations.
v. Obstacle clearance surface (OCS). Level or sloping surface used for obstacle evaluation. The separation between this surface and specified minimum altitude, glidepath angle or minimum required climb path defines the MINIMUM required obstruction clearance at any given point.
w. 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 method 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.
x. Proponent. The originator of a DP requirement. This may include an individual user group, ATC, Aeronautical Information Services, or other appropriate government agency.
y. Radar SID. A SID established when ATC has a need to vector aircraft on departure to a particular ATS Route, NAVAID, or fix.
z. RNAV DP. A DP developed for RNAV-equipped aircraft whose ground track is based on satellite or DME/DME navigation systems.
aa. Required Navigation Performance (RNP). A statement of the 95 percent navigation accuracy performance that meets a specified value for a particular phase of flight or flight segment and incorporates associated on-board performance monitoring and alerting features to notify the pilot when the RNP for a particular phase or segment of a flight is not being met.
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 and/or maintains instrument flight procedures.
Appendix A › 4. Acronym List
dd. 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.
ee. Standard instrument departure (SID). A preplanned instrument flight rule (IFR) air traffic control (ATC) departure procedure printed for pilot/controller use in graphic form 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 always be received prior to flying a SID.
ff. SID transition. A published segment used to connect the SID to one or several en route airways/jet routes.
gg. Terminal Area Route Generation Evaluation and Traffic Simulation (TARGETS). An air traffic tool for RNAV DP design.
hh. Top altitude. In reference to SID published altitude restrictions, the charted “maintain” altitude contained in the procedure description or assigned by ATC.
ii. Transmittal letter (TL). A biweekly publication, prepared by Aeronautical Information Services, used as the medium to promulgate instrument approach procedures and textual ODPs and their effective dates for publication.
jj. Visual climb over airport (VCOA). A departure option to allow an aircraft to climb over the airport with visual references to obstacles to attain a suitable altitude from which to proceed with the instrument portion of the departure. VCOA procedures are developed to avoid obstacles greater than three SM from the departure end of the runway as an alternative to complying with climb gradients greater than 200 ft/NM. These procedures are either published in the “Takeoff Minimums and (Obstacle) Departure Procedures, and Diverse Vector Area (Radar Vectors)” section of the Terminal Procedures Publications or as an option on a Graphic ODP.
kk. Waypoint (WP). A predetermined geographical position used for route definition and progress reporting purposes that is defined by latitude/longitude. For VOR/DME systems, it is defined by the radial/distance of the position from the reference facility.
4. Acronym List
AAO Adverse Assumption Obstacle AAUP Attention All Users Page AER Approach End of Runway AGL Above Ground Level AIRAC Aeronautical Information, Regulation, and Control ARTCC Air Route Traffic Control Center ASOS Automated Surface Observing System ATC Air Traffic Control ATS Air Traffic System
AWOS Automated Weather Observing System CF Course to Fix CFR Code of Federal Regulations CG Climb Gradient CTAF Common Traffic Advisory Frequency DER Departure End of Runway DF Direct to Fix DME Distance Measuring Equipment DP Departure Procedure DRP Departure Reference Point DVA Diverse Vector Area FB Fly By FM Course from Fix to Manual Termination FMS Flight Management System FO Fly Over FPT Flight Procedures Team GPS Global Positioning System IAC Interagency Air Committee IAP Instrument Approach Procedure ICA Initial Climb Area ICAO International Civil Aviation Organization IDF Initial Departure Fix IF Initial Fix IFP Instrument Flight Procedure IFR Instrument Flight Rules IMC Instrument Meteorological Conditions IRU Inertial Reference Unit KIAS Knot Indicated Airspeed LNAV Lateral Navigation MEA Minimum En route Altitude MIA Minimum IFR Altitude MOA Military Operating Area MOCA Minimum Obstacle Clearance Altitude MRA Minimum Reception Altitude MSL Minimum Sea Level MVA Minimum Vectoring Altitude NAS National Airspace System NAVAID Navigational Aid NDB Non-directional Beacon NFDD National Flight Data Digest NM Nautical Mile NOTAM Notices to Airmen OCS Obstacle Clearance Surface ODP Obstacle Departure Procedure OEA Obstacle Evaluation Area OSG Operations Support Group
5. Related Publications. › a. FAA Orders and Advisory Circulars:
OTA Other Transactional Authority PBN Performance Based Navigation P-NOTAM Permanent NOTAM POC Point of Contact RF Radius to Fix RNAV Area Navigation RNP Required Navigation Performance RVR Runway Visual Range SID Standard Instrument Departure SIT Site Implementation Team SM Statute Mile TACAN Tactical Air Navigation TC True Course TERPS Terminal Instrument Procedures TF Track to Fix TL Transmittal Letter VA Heading to Altitude VCA Visual Climb Area VCOA Visual Climb Over Airport VFR Visual Flight Rules VI Heading to Intercept VM Heading to Manual Termination VOR Very High Frequency Omni-directional Range VORTAC Very High Frequency Omni-directional Range/TACAN
5. Related Publications.
a. FAA Orders and Advisory Circulars:
• Advisory Circular 90-100, United States Terminal and En route Area Navigation (RNAV) Operations.
• Advisory Circular 90-105, Approval Guidance for RNP Operations and Barometric Vertical Navigation in the U.S. National Airspace System.
• Order 1100.161, Air Traffic Safety Oversight.
• Order 7100.9, Standard Terminal Arrival Program and Procedures.
• Order 7210.3, Facility Operation and Administration.
• Order 7400.2, Procedures for Handling Airspace Matters.
• Order JO 7470.1, DME/DME Infrastructure Evaluation for Area Navigation (RNAV) Routes and Procedures.
• Order 8260.3, United States Standard for Terminal Instrument Procedures.
Appendix A › 7. Information Update.
• Order 8260.19, Flight Procedures and Airspace.
• Order 8260.26, Establishing and Scheduling Standard Instrument Procedure Effective Dates.
• Order 8260.42, United States Standard for Helicopter Area Navigation.
• Order 8260.43, Flight Procedures Management Program.
• Order 8260.58, United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design.
b. Other documents:
• IAC No. 4, Interagency Air Committee Chart Specification for Instrument Approach Procedures and Airport Diagrams.
• IAC No. 7, Interagency Air Committee Chart Specification for Graphic Instrument Departure Procedure Charts.
• IAC No. 17, Interagency Air Committee Chart Specification for Terminal Procedures Publications.
• RTCA DO-187, Minimum Operational Performance Standards for Airborne Area Navigation Equipment Using Multi-Sensor Inputs.
6. Forms and Reports. Appendices B, C, D, E, F, and G contain requirements data, applicable forms, and associated instructions.
7. Information Update. For your convenience, 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.
6. Line 6 - Route. › c. Line 6.3 - ATC Requested Routing/Operational Parameters. Enter any…
Appendix B. Instructions for Completing Graphic
Departure Procedure (DP) Requirements Worksheet
Instructions for completing the graphic departure procedure requirements worksheet by other than Aeronautical Information Services 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 ID(s). Enter 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. Charting of the Departure Control frequency will occur automatically (without coordination). Other communication types will be depicted only when specifically requested. For additional frequencies requested by the IFP Validation Team or specified on the worksheet, specify Chart ATIS, CLNC DEL, etc.
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.
11. Line 11 - Remarks. › b. Enter appropriate information to clarify a data entry; e.g.,…
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 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.
f. Line 6.6 - Enter the “Top Altitude(s)” (SID Only). For multiple airports, include the Airport Identifier and/or specific runways when “Top Altitudes” differ between airports and/or runways [see paragraph 2-1-1.e(2)(f)].
7. Line 7 - Transitions. (NA for 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.
b. Enter appropriate information to clarify a data entry; e.g., airspeed restriction for air traffic, maximum altitude for aircraft performance, etc.
c. If the proposed DP does not meet the criteria requirements in paragraph 2-1-1, a statement of justification is necessary to explain why a DP is required. Avoid publication of unnecessary DPs.
Continue reading ↓ 120 of 278 passages shown