Order 8260.46K Departure Procedure (DP) Program
To manage the Departure Procedure (DP) program, this order provides policy, guidance, and standardization for initiating, designing, documenting, and processing for DPs prescribed under Title 14, Code of Federal Regulations (14 CFR) part 97 as well as other DPs not specified under part 97. This order also contains guidance that is pertinent to 14 CFR parts 1, 71, 77, 91, 95, 121, 125, 129, 135, and 171.
Text read by OCR from a scanned file (20 of 155 pages). Check the original, as some words may be misread.
Cover Page
Distribution: Electronic Distribution Initiated By: AFS-400
ORDER 8260.46K
This order provides the policy, guidance, and standardization for initiating, designing, processing, and managing the departure procedure program in the United States and its territories.
Jackie L. Black, Jr. for Lawrence Fields Executive Director, Flight Standards Service
Effective Date:
07/01/2024
National Policy
SUBJ: Departure Procedure (DP) Program
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 1-1-6. Word Meanings … 1-1
Chapter 2. Responsibilities … 2-1
Section 2-1. DP Guidelines … 2-1
2-1-1. General … 2-1 2-1-2. Obstacle Departure Procedures (ODP) … 2-4 2-1-3. Standard instrument departures … 2-20 2-1-4. Design constraints … 2-20 2-1-5. Responsibilities … 2-30 2-1-6. Accuracy Verification and Responsibilities … 2-35 2-1-7. Military DPs … 2-35 2-1-8. FAA 8260-15 Series Forms … 2-36 2-1-9. Periodic Review … 2-37 2-1-10. Procedure Amendments … 2-37
Chapter 3. Graphic Instrument Departure Procedures (DPs) … 3-1
Section 3-1. General Guidance … 3-1
3-1-1. General … 3-1 3-1-2. Minimum Safe Altitude (MSA) … 3-3 3-1-3. Naming of DPs … 3-4 3-1-4. Transition Naming … 3-5 3-1-5. Computer Identification Codes … 3-5 3-1-6. RNAV DPs … 3-5 3-1-7. Examples of Various Graphic Departure Scenarios … 3-8
Appendix A. Administrative Information … A-1
Section 1. General … A-1
Section 2. Acronyms and Abbreviations … A-4
Section 3. Definitions … A-5
Appendix B. Graphic Departure Procedure (DP) Requirements Worksheet … B-1
Section 1. Instructions for Completing the Graphic DP Requirements Worksheet … B-1
ii
Appendix C. FAA Form 8260-2, Data Worksheet … C-1
Section 1. Instructions for Completing the Graphic DP Requirements Worksheet … C-1
Appendix D. FAA Form 8260-15A, Takeoff Minimums and Obstacle Departure Procedures (ODP) and Sample Forms … D-1
Section 1. Instructions for Completing FAA Form 8260-15A … D-1
Section 2. Instructions for Completing FAA Form 8260-15B, Graphic Departure Procedure (DP) (non-RNAV DP) … D-12
Appendix E. FAA Form 8260-15B, Graphic Departure Procedures (RNAV) … E-1
Section 1. Instructions for Completing FAA Form 8260-15B (RNAV DPs) … E-1
Section 2. Instructions for Completing FAA Form 8260-15C, Departure (Data Record) .... E-27
Section 3. Instructions for Completing FAA Form 8260-15E, RNAV Departure Procedure Attention All Users Page (AAUP) (RNAV Departure Procedure) … E-41
Appendix F. Helicopter RNAV DP … F-1
Appendix G. FAA Form 8260-15D, Diverse Vector Area … G-1
Section 1. Instructions for Completing FAA Form 8260-15D … G-1
1-1-6. Word Meanings. › c. May.
Chapter 1. General Information
Section 1-1. Basic
1-1-1. Purpose of this order. To manage the Departure Procedure (DP) program, this order provides policy, guidance, and standardization for initiating, designing, documenting, and processing for DPs prescribed under Title 14, Code of Federal Regulations (14 CFR) part 97 as well as other DPs not specified under part 97. This order also contains guidance that is pertinent to 14 CFR parts 1, 71, 77, 91, 95, 121, 125, 129, 135, and 171.
1-1-2. Audience. All personnel who are responsible for DP design, documentation, and processing.
1-1-3. Where you can find this order. You can find this order on the FAA’s website.
1-1-4. What this order cancels. Order 8260.46J, Departure Procedure (DP) Program, dated 07/12/2022.
1-1-5. Explanation of changes. Significant areas of new direction, guidance, policy, and criteria are as follows:
a. Administrative. Corrections have been made throughout the order.
b. Updated guidance.
(1) Guidance for the initial climb area has been updated throughout the order.
(2) Minimum en route instrument flight rules altitude and minimum obstruction clearance altitude documentation requirements have been updated throughout the order.
(3) Updated magnetic variation documentation requirements.
(4) Updated requirements for FAA Form 8260-15A, Takeoff Minimums and Textual Departure Procedures (DP), at private-use civil airports/heliports/seaplane bases not open to the public.
1-1-6. Word Meanings. Word meanings as used in this order:
a. Must. This means that application of the criteria is mandatory.
b. Should. This means that application of the criteria is recommended.
c. May. This means that application of the criteria is optional.
2-1-1. General. › f. Apply “Legacy” criteria as follows:
Chapter 2. Responsibilities
Section 2-1. DP Guidelines
2-1-1. General. Instrument flight rules (IFR) DPs may be designed and published for all runways authorized by the approving authority. There are two types of DPs: those designed to assist pilots in obstruction avoidance [referred to as obstacle departure procedure (ODP)] and those designed to communicate air traffic control (ATC) clearances [referred to as standard instrument departure (SID)]. Design, document, process, and chart helicopter point-in-space (PinS) departures as a SID [see appendix F].
a. Instrument flight procedures (IFPs) must be designed, documented, and processed in accordance with these standards; however, obstacles, navigation information, or traffic congestion may require special consideration, where justified by operational requirements. When IFPs cannot be designed/documented in accordance with applicable standards, apply Order 8260.3, United States Standard for Terminal Instrument Procedures (TERPS), paragraph 1-4-2.
b. Where IFR DPs are authorized by the approving authority, conduct a diverse departure assessment (see Order 8260.3). Do not conduct a diverse departure assessment for helicopter departures. Helicopter IFR diverse departures are not authorized; visual or visual flight rules (VFR) departures to an initial departure fix (IDF) may be authorized.
c. When IFR DPs are not authorized due to a diverse assessment, identify runway/helipad and reason on FAA Form 8260.15A, Takeoff Minimums and Obstacle Departure Procedures (ODP), [see appendix D, section 1, paragraph 2.e.(1)].
d. Use the term “Legacy” as follows:
(1) When text in this order uses the word “Legacy” it authorizes policy/guidance associated with a previous standard that is considered valid until the current standard is implemented for all DPs.
(2) When “Legacy” is used in a sentence, the sentence is considered legacy policy/guidance, not the whole paragraph.
(3) When “Legacy” is used for the title of a figure/table, it applies to the whole figure/table.
e. Order 8260.3 defines initial climb area (ICA) criteria as follows:
(1) An ICA without sections (see Order 8260.3, figure 13-1-3) identified using the term “Legacy.”
(2) An ICA with sections 1 and 2 (see Order 8260.3, figure 13-1-4).
f. Apply “Legacy” criteria as follows:
(1) At airports where only an ODP is published or a new ODP is being added (No SID/ diverse vector areas (DVAs) is published), the ODP must not be amended/designed using “Legacy” criteria.
2-1-1. General. › j. When documentation requires the airport ID, define the FAA airport…
(2) At airports with a published ODP where SIDs/DVAs are being added, both must not be designed using “Legacy” criteria (see paragraph 2-1-1.d).
(3) At airports where SIDs/DVAs and ODP are published or new SIDs/DVAs are being added, the design must use the legacy criteria unless requested by a proponent (see paragraph 2- 1-6.b.).
(4) When not implementing the legacy ICA criteria, all DPs and DVAs, both textual and graphic, at the airport must be updated in the same publication cycle. For example, when requested, the legacy ICA is not used for an original SID at the primary airport, apply the same ICA criteria to all runways servicing that airport. However, other airports served by the original SID may use the legacy ICA as requested by the proponent.
g. All DPs and DVAs at an airport must use the same ICA criteria. When adding or amending, all must be charted in the same publication cycle.
h. When designing new or amending DPs, ensure all DPs are updated when they share an identical segment. For example, when evaluating the ICA of a new SID and a low, close-in obstacle, ceiling/visibility, or a climb gradient (CG) change(s), as applicable, then ensure the other DPs at the same airport are updated in the same publication cycle as well.
i. Document the ICA criteria and the Order 8260.3 version, including the change when applicable, used for the DP in the remarks section of the applicable FAA Form 8260-15 (see paragraph 2-1-1.f.(4)). When a DP serves multiple airports, document the airport identification (ID) associated with the ICA design used for the procedure design and evaluation.
Example:
Single Airport: “ORDER 8260.3X – CHG X, LEGACY ICA USED FOR DESIGN AND EVALUATION.” or “ORDER 8260.3X – CHG X, ICA USED FOR DESIGN AND EVALUATION.”
Example:
Multiple airports: “ZZZ: ORDER 8260.3X – CHG X, LEGACY ICA USED FOR DESIGN AND EVALUATION; XXX, YYY: ORDER 8260.3X – CHG X, ICA USED FOR DESIGN AND EVALUATION.”
j. When documentation requires the airport ID, define the FAA airport ID as derived from National Airspace Resource (NASR) and, when applicable, the ICAO ID when available for locations outside the contiguous United States. Separate the airport ID and the ICAO ID with a slash, even though charting may use parentheticals.
2-1-1. General. › l. To assist pilots with identifying the ICA vs legacy ICA, the charted…
Example:
“XXX” or “ABC/PDEF”
k. When documentation requires a signature, document the responsible individual as outlined below, their organization's office identification, and the date signed on the applicable line of the appropriate FAA Form 8260-15.
(1) FLIGHT INSPECTED BY: Enter the name of the pilot who conducted the flight inspection/validation.
(2) DEVELOPED BY: Enter the individual who was responsible for the design of the procedure being submitted.
(3) APPROVED BY: Enter the name of the organization's individual responsible for the approval of the procedure being submitted. The signature in this block certifies that the procedure:
(a) Was developed in accordance with appropriate policies, directives, standards, and criteria.
(b) Is approved for further processing.
l. To assist pilots with identifying the ICA vs legacy ICA, the charted procedure must bold/underline certain entries as follows (do not follow this for FAA Form 8260-15 series documentation; this is for charting only):
(1) When applying legacy ICA design criteria, do not bold/underline entries (even when the applicable FAA Form 8260-15 may).
(2) Textual: When applying ICA design criteria, bold/underline as indicated in the following examples as applicable:
Example:
TAKEOFF MINIMUMS:
Rwy (number):
DEPARTURE PROCEDURE:
Rwy (number):
VCOA:
Rwy (number):
TAKEOFF OBSTACLE NOTES:
2-1-2. Obstacle Departure Procedures (ODP). › b. Establish only one ODP for a runway.
Rwy (number) Low, Close-in Obstacles: Rwy (number) Takeoff Minimums Obstacles:
(3) Graphic: Chart takeoff obstacle notes only for graphic ODPs. When applying ICA design criteria, bold/underline as indicated in the following examples as applicable:
Example:
TAKEOFF MINIMUMS:
Rwy (number):
TAKEOFF OBSTACLE NOTES:
Rwy (number) Low, Close-in Obstacles: Rwy (number) Takeoff Minimums Obstacles:
In the departure route description section:
TAKEOFF RUNWAY (number): or TAKEOFF ALL RUNWAYS: VCOA RUNWAY (number): or VCOA ALL RUNWAYS:
2-1-2. Obstacle Departure Procedures (ODP). Design 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. The following rules apply to ODPs:
a. The primary goal in ODP design is to retain standard takeoff minimums with standard CG to the extent possible.
b. Establish only one ODP for a runway.
(1) This will be considered the default IFR DP for a given runway and is intended for pilot awareness and use in the absence of ATC radar vectors or SID assignment.
(2) For special DPs, ODPs are not required for private-use civil airports/heliports/seaplane bases not open to the public provided the following is applied:
(a) This applies only when the ODP and SID use the same diverse assessment.
(b) If a DP is requested and an ODP is not required by the airport/heliport/seaplane base owner, a SID must be designed as the default DP.
(c) Do not reference the graphic SID on FAA Form 8260-15A. An FAA Form 8260-15A is not required since FAA Form 8260-15B, Graphic Departure, is used.
(d) Do not reference FAA Form 8260-15A on FAA Form 8260-7A, Special Instrument Approach Procedure, for approaches. The obstacles must be listed on the SID.
2-1-2. Obstacle Departure Procedures (ODP). › Design ODPs with primary emphasis given to using the least onerous…
(e) The SID documentation must contain all low, close-in obstacles and associated minimums with CGs as applicable on FAA Form 8260-15B.
(f) FAA Form 8260-7B will contain a note for the SID and all approaches stating an ODP is not published and all departure information and minimums are listed on the SID.
(3) 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.”
c. Depict an ODP either textually or graphically within the following guidelines.
(1) Textual ODP. A relatively simple ODP may be published textually unless a graphical depiction is required for clarity.
(2) A graphic depiction is required if any of the following conditions exist:
(a) More than one turn (“climbing right turn on radial R-xxx” is considered two turns);
(b) More than one altitude change;
(c) More than one speed restriction;
(d) A DME ARC or holding is part of the departure instructions.
(3) The decision to graphically publish ODPs when not required by this order rests with the service provider. When determining the need for a graphic DP, the service provider must, in addition to the textual DP restrictions noted above, consider:
(a) The number of ground-based navigational aids (NAVAIDs) and fixes;
(b) Whether graphical depiction will enhance pilot comprehension of the procedure, and
(c) The proximity and effect of precipitous or significant terrain.
(4) Graphic ODP. Complex ODPs are those that require a visual presentation to communicate the departure instructions clearly and desired flight paths. If the ODP is depicted graphically, it must be clearly stated on FAA Form 8260-15A in the Departure Procedure section, e.g., “USE JONES DEPARTURE.”
d. 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.
e. Design ODPs with primary emphasis given to using the least onerous method (see appendix A definition) 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.
2-1-2. Obstacle Departure Procedures (ODP). › i. When applicable, design ODPs using ground-based NAVAIDs, area…
f. ODPs may include a CG when required for obstruction avoidance and/or lateral navigation (LNAV) engagement [see Order 8260.58, U.S. Standard for Performance Based Navigation (PBN) Instrument Procedure Design, paragraph 5-1-1.c.(2)]; however, CGs, speed, and/or altitude restrictions solely for ATC purposes are not allowed.
g. 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 the route flown.
h. Transition routes are not permitted on ODPs.
i. When applicable, design ODPs using ground-based NAVAIDs, area navigation (RNAV), or dead reckoning (DR) guidance wherever possible. Do not specify radar vectors for navigation guidance in ODP design. At those locations served by RNAV approaches exclusively, every effort must first be made to design an ODP that accommodates conventional [preferably very high frequency omni-directional range (VOR)] navigation systems. If this effort fails, design an RNAV ODP.
(1) 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 paragraph 2-1-3.e.(3)(c)).
(2) Do not establish a VCOA in conjunction with an RNAV ODP.
(3) VCOAs must be established as required by Order 8260.3 paragraph 13-2-2.b.(4)(b) and 13-2-2.b.(5)(a) except where Flight Procedures and Airspace Group (FPAG) have approved an ATC request to opt-out. 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.
(4) 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.
(5) 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.
(6) Publish a helicopter PinS DP as a SID. ODPs are not authorized (see appendix F).
2-1-3. ODP Documentation for Specific Design Combinations (see appendix A, section 1, paragraph 2. Background). Document an ODP and/or standard/non-standard takeoff minimums based on the diverse departure assessment application as described in Order 8260.3. The
2-1-3. ODP Documentation for Specific Design Combinations. › c. Obstacle penetrations within ICA are identfied as low, close-in…
following guidance/policy applies to ODP takeoff minimums, obstacles (takeoff/low, close-in), and route documentation (see as applicable, examples in appendix D, sections 1 and 2, examples in appendix E, section 1, and background in appendix A).
a. General Guidance/Policy.
(1) Legacy takeoff obstacle notes. When takeoff obstacle notes are required, using this paragraph, document using a note identifying the obstacle(s) type, location relative to departure end of runway (DER)/extended runway centerline (RCL), height (AGL), and elevation (MSL) (see appendices D and E for recommended publication text available). Do not apply paragraph 2-1-3.a.(3).
(2) Adverse assumption obstacle (AAO). Do not document/publish an AAO as a “takeoff obstacle” because pilots are not familiar with the AAO concept. However, publishing a ceiling and visibility will allow for those situations where the CG cannot be achieved and still afford the pilot the opportunity to visually acquire and avoid any obstruction that could have been built without notice to the FAA.
(3) Takeoff obstacle notes. Document low, close-in obstacles separately from takeoff minimums obstacles; do not group them (see Order 8260.3, paragraph 13-1-1.d.(1) and (2) regarding the terms low, close-in obstacles and takeoff minimums obstacles).
(4) Document takeoff obstacle notes for textual ODPs on FAA Form 8260-15A and for graphic ODPs on FAA Form 8260-15B.
b. No obstacle penetrations. When diverse departure obstacle assessment does not identify any obstacle penetrations, standard takeoff minimums apply. Document “…STANDARD.” in the Takeoff Minimums section of FAA Form 8260-15A.
c. Obstacle penetrations within ICA are identified as low, close-in obstacles. When a diverse departure obstacle assessment identifies low, close-in obstacles, document the obstacles in the Takeoff Obstacles Notes section of the applicable FAA Form 8260-15A/B.
(1) For low, close-in obstacle penetrations 35 feet and below, document the following (see example 1):
(a) When all low, close-in obstacles penetrate by 35 feet and below document as: “…OBSTACLES 35 FT AND BELOW…”
(b) Based on the evaluation, follow the obstacle(s) description with a height to cross DER that clears all takeoff obstacle(s) (low, close-in) with the phrase “…CROSSING DER 34 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES…”
(2) Document the obstacle(s) that penetrate the OCS more than 35 feet as follows (see example 2):
(a) List obstacle(s) type as applicable. When identifying obstacles, be as descriptive as reasonably possible so as to provide the pilot a clear understanding of what to prepare and/or
look for; e.g., instead of just saying “POWER POLES,” it would be more helpful to use the descriptor of “POWER LINES” in some instances. Another example would be instead of just saying “TERRAIN,” if applicable, the use of “RIDGELINE” or “BLUFF” would provide a clearer picture. Phrases such as “MULTIPLE ANTENNAS, NUMEROUS TREES, etc.” are acceptable.
(b) List the obstacle(s) distance (inner/outer limits from DER) as applicable. Distance will be indicated with 500 feet or quarter nautical mile (NM) intervals from DER to a maximum of 2.6 NM as follows:
(c) Describe the obstacle(s) inner limits less than 500 feet from DER as “WITHIN 500 FT FROM DER”; no outer limit is required.
(d) For a single obstacle, no outer limit is required. Round the distance from DER up as described in (e) below.
(e) For more than one obstacle, define the inner and outer limits in relationship to the DER. The inner limit must start at the closest obstacle to DER rounded down (e.g., 0 – 499 is described as “WITHIN 500 FT,” 500 – 999 feet rounds down to 500 feet, 1000-1518 feet rounds down to 1000 feet, 1519 - 3037 feet rounds down to 1/4 NM, …2.5 NM to 2.6 NM rounds down to 2.5 NM). The outer limit of the obstacles must use the furthest obstacle distance from DER, rounded up to 2.6 NM maximum (e.g., 500 – 1000 feet rounds up to 1000 feet, 1001 - 1500 feet rounds up to 1500 feet, 1501 - 1519 rounds up to 1/4 NM, 1520 - 3037 feet rounds up to 1/2 NM, … more than 2.5 NM rounds to 2.6 NM). Specify distances less than 1 NM in feet until 1/4 NM, then use 1/4 NM increments to 1 NM. Specify distances 1 NM or greater to the nearest whole and tenth of a NM. Describe the limits using the words “BEGINNING” and “EXTENDING TO.”
(f) Document the obstacle(s) horizontal limits in relationship to the extended centerline of the runway. Use one of the following descriptions, as applicable: “LEFT OF CENTERLINE,” “RIGHT OF CENTERLINE,” “LEFT AND RIGHT OF CENTERLINE,” “CROSSING CENTERLINE,” “LEFT AND CROSSING CENTERLINE,” “RIGHT AND CROSSING CENTERLINE,” or “LEFT, RIGHT, AND CROSSING CENTERLINE.” Obstacles +/- 100 feet left or right of centerline are considered crossing centerline.
(g) Based on the evaluation document, the MSL elevation and the height above DER are as follows: single obstacle - “… 144 FT MSL, 64 FT ABOVE DER...” or multiple obstacles - “…UP TO 5176 FT MSL, 77 FT ABOVE DER…”
(h) Based on the evaluation, apply paragraph 2-1-3.c.(1)(b).
(3) When both low, close-in obstacle penetrations 35 feet and below and penetrations by more than 35 feet within the ICA are present, only document the obstacles more than 35 feet (see example 3).
2-1-3. ODP Documentation for Specific Design Combinations. › d. Obstacle penetrations within ICA other than low, close-in obstacles.
Example 1: Low, close-in obstacle penetrations 35 feet and below within the ICA.
TAKEOFF OBSTACLE NOTES:
RWY 8 LOW, CLOSE-IN OBSTACLES: OBSTACLES 35 FT AND BELOW. CROSSING DER 5 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
Example 2: Low, close-in obstacle penetrations more than 35 feet within the ICA.
TAKEOFF OBSTACLE NOTES:
RWY 8 LOW, CLOSE-IN OBSTACLES: TREES AND SIGN BEGINNING 1000 FT FROM DER EXTENDING TO 3/4 NM, CROSSING CENTERLINE, UP TO 346 FT MSL, 128 FT ABOVE DER. CROSSING DER 52 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
Example 3: Both low, close-in obstacle penetrations 35 feet and below and penetrations by more than 35 feet within the ICA.
TAKEOFF OBSTACLE NOTES:
RWY 8 LOW, CLOSE-IN OBSTACLES: TREES AND SIGN BEGINNING 1000 FT FROM DER EXTENDING TO 3/4 NM, CROSSING CENTERLINE, UP TO 658 FT MSL, 128 FT ABOVE DER. CROSSING DER 52 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
d. Obstacle penetrations within ICA other than low, close-in obstacles. When diverse departure obstacle assessment identifies penetrating obstacles inside the ICA (other than low, close-in obstacles), document applicable takeoff obstacle notes and minimums in the Takeoff Obstacles Notes and the Takeoff Minimums sections of the applicable FAA Form 8260-15A/B.
(1) Takeoff Obstacle Notes (other than low, close-in): document takeoff minimums obstacle notes (both obstacle penetrations 35 feet and below and penetrations by more than 35 feet) using the same format as paragraph 2-1-3.c.(2) except end the phrase in paragraph 2-1-3.c.(1)(b) with “…CLEARS TAKEOFF MINIMUMS OBSTACLES…” (see example 1).
Example 1: Takeoff minimums obstacle penetrations only in ICA other than low, close-in (all obstacles penetrate 35 feet and below).
TAKEOFF OBSTACLE NOTES:
RWY 8 TAKEOFF MINIMUMS OBSTACLES: TOWER 2.6 NM FROM DER, LEFT OF CENTERLINE, 2395 FT MSL, 391 FT ABOVE DER. CROSSING DER 4 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES.
(2) Takeoff Minimums (does not apply to low, close-in obstacles; see examples 2 and 3):
(a) When using a ceiling and visibility to see and avoid the obstacle(s), document a ceiling and visibility with the option of standard takeoff minimums and with a minimum CG to a specified fix or altitude that provides obstacle clearance with a standard CG in the following format: “…400-3 OR STANDARD WITH MINIMUM CLIMB OF 300 FT/NM TO 4300…” Identify the obstacle(s) on which the published ceiling and visibility are based in the Controlling Obstacles section.
(b) Document a DER crossing height option in takeoff minimums, which clears all penetrating takeoff minimum obstacles based on 200 ft/NM CG in the following format: “…CROSSING DER 66 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES...” Identify the obstacle(s) on which the published DER crossing height is based in the Controlling Obstacles section.
(c) When a reduced takeoff runway length is used to mitigate obstacles [all must penetrate by 35 feet and below (excluding low, close-in)], document in takeoff minimums an option which clears all penetrating takeoff minimums obstacles in the following format: “…ALTERNATIVELY, WITH STANDARD TAKEOFF MINIMUMS AND A NORMAL 200 FT/NM CLIMB GRADIENT, TAKEOFF MUST OCCUR NO LATER THAN 1800 FT PRIOR TO DER…”
Example 2: Takeoff minimums obstacle penetrations only in ICA other than low, close-in (all obstacles penetrate 35 feet and below).
TAKEOFF MINIMUMS:
RWY 8: 400-3 OR STANDARD WITH MINIMUM CLIMB OF 204 FT/NM TO 1200 OR STANDARD AND CROSSING DER 35 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES. ALTERNATIVELY, WITH STANDARD TAKEOFF MINIMUMS AND A NORMAL 200 FT/NM CLIMB GRADIENT, TAKEOFF MUST OCCUR NO LATER THAN 1300 FT PRIOR TO DER.
Example 3: Takeoff minimums obstacle penetrations only in ICA other than low, close-in (obstacles penetrate by both 35 feet and below, and more than 35 feet).
TAKEOFF MINIMUMS:
RWY 8: 400-3 OR STANDARD WITH MINIMUM CLIMB OF 204 FT/NM TO 1200 OR STANDARD AND CROSSING DER 67 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES.
e. Obstacle penetrations outside of ICA. When diverse departure obstacle assessment identifies penetrating obstacles outside the ICA, document the textual route/sector or graphic route under the Textual Departure Procedure Section (FAA Form 8260-15A) or DP Route Description Section (FAA Form 8260-15B) and the takeoff minima in the Takeoff Minimums Section on the applicable FAA Form 8260-15A/B as follows (see examples 1, 2, and examples in appendix D, sections 1 and 2):
2-1-3. ODP Documentation for Specific Design Combinations. › e. Obstacle penetrations outside of ICA.
(1) Document a textual route/sector or graphic route as follows: “…RWY 8: CLIMBING LEFT TURN HEADING 330.01 AND ABC VOR/DME R-318 TO VIPER…” or “… RWY 12: CLIMB ON A HEADING BETWEEN 061.10 CW TO 228.08 FROM DEPARTURE END OF RUNWAY…” or “…RWY 8: MINIMUM CLIMB OF 260 FT/NM TO 8700 FOR HEADINGS 229.03 CW TO 300.32…”
(2) Document a minimum CG to a specified fix or altitude that provides obstacle clearance to allow standard takeoff minima as follows: “…RWY 8: STANDARD WITH MINIMUM CLIMB OF 228 FT/NM TO 2200…”
(3) Document a minimum CG, ceiling and visibility, and instructions for a visual climb over airport (VCOA) in the takeoff minimums section of the applicable FAA Form 8260-15A/B as follows (see appendix D, section 1, paragraph 2.i.(4) for controlling obstacle documentation):
(a) When documenting a VCOA in the takeoff minimums, describe the ceiling and visibility in the following format: “…[CIG (value)-VSBY (value)] FOR VCOA...”
(b) Document VCOA instructions in the Visual Climb Over Airport section of FAA Form 8260-15A or the DP route description section of FAA Form 8260-15B as applicable.
(c) Documentation must contain a list of associated runways (“VCOA RWY 18, 36:…”) or the statement “VCOA ALL RWYS:…”, followed by “…OBTAIN ATC APPROVAL FOR VCOA WHEN REQUESTING IFR CLEARANCE…”, then the VCOA instructions.
(d) The VCOA must include instructions to climb in visual conditions to cross a location/fix at or above the climb to altitude as follows:
1. For a VCOA diverse, include the instruction, “…BEFORE PROCEEDING ON COURSE…” following the climb to altitude as follows: “…CLIMB IN VISUAL CONDITIONS TO CROSS CASTLE AIRPORT AT OR ABOVE 2200 BEFORE PROCEEDING ON COURSE.”
2. For a VCOA route departure, specify the intended direction of flight to cross the first fix of the route, followed by the climb to altitude, and then specify the route (see Order 8260.3 figure 13-4-5) as follows: “…CLIMB IN VISUAL CONDITIONS TO CROSS PSTOL EASTBOUND AT OR ABOVE 5000, THEN ON LEX VOR/DME R-281 TO LEX.” Detail the makeup of any fix specified in the VCOA instructions that is not published on a en route or graphic ODP/SID chart as follows: “…CLIMB IN VISUAL CONDITIONS TO CROSS PEETE (AGC 040/16.01 DME) NORTHBOUND AT OR ABOVE 2000…”).
Example 1: FAA Form 8260-15A, Obstacle penetration(s) outside ICA.
TAKEOFF MINIMUMS:
RWY 8: STANDARD WITH MINIMUM CLIMB OF 251 FT/NM TO 1600, OR 1300-3 FOR VCOA.
TEXTUAL DEPARTURE PROCEDURE:
RWY 8: CLIMB ON HEADING 082.18 TO 1200 BEFORE TURNING LEFT.
VISUAL CLIMB OVER AIRPORT:
RWY 8: OBTAIN ATC APPROVAL FOR VCOA WHEN REQUESTING IFR CLEARANCE. CLIMB IN VISUAL CONDITIONS TO CROSS METRO AIRPORT AT OR ABOVE 5000 BEFORE PROCEEDING ON COURSE.
Example 2: FAA Form 8260-15B (Graphic ODP), Obstacle penetration(s) outside ICA.
DP ROUTE DESCRIPTION:
TAKEOFF RWY 18: CLIMB ON HEADING 185.22 TO 7700, THEN CLIMBING LEFT TURN DIRECT MKM VOR/DME, THEN ON MKM R-028 TO LARST, THENCE…
TAKEOFF RWY 36: CLIMB ON HEADING 005.22 TO 7100, THEN CLIMBING RIGHT TURN ON MKM R-028 TO LARST, THENCE…
VCOA ALL RUNWAYS: OBTAIN ATC APPROVAL FOR VCOA WHEN REQUESTING IFR CLEARANCE. CLIMB IN VISUAL CONDITIONS TO CROSS MKM VOR/DME NORTHEASTBOUND AT OR ABOVE 8100, THEN ON MKM R-028 TO LARST, THENCE…
… CROSS LARST AT OR ABOVE MEA/MCA FOR ROUTE OF FLIGHT.
TAKEOFF MINIMUMS:
RWY 8: STANDARD WITH MINIMUM CLIMB OF 251 FT/NM TO 1600, OR 1300-3 FOR VCOA.
f. Obstacle penetrations both inside and outside of ICA. When diverse departure obstacle assessment identifies obstacle penetrations both inside and outside of ICA, apply applicable guidance in paragraphs 2-1-3.c, d and/or e based on the following:
(1) For low, close-in obstacle penetrations, apply paragraph 2-1-3.c.
(2) When the CG within the ICA is higher than the CG outside the ICA, apply paragraph 2-1-3.d. except document the altitude sufficient to clear all obstacles within/outside the ICA.
2-1-3. ODP Documentation for Specific Design Combinations. › f. Obstacle penetrations both inside and outside of ICA.
(3) When the CG within the ICA is lower than the CG outside the ICA, apply paragraph 2-1-3.e. except document the altitude sufficient to clear all obstacles within/outside the ICA.
Example 1: FAA Form 8260-15A: ODP with low, close-in obstacle penetrations less than 35 feet; low, close-in obstacle penetrations more than 35 feet; takeoff minimums obstacle penetrations in ICA; and obstacle penetrations outside ICA. Highest CG within ICA.
TAKEOFF MINIMUMS:
RWY 8: 300-1 3/4 WITH MINIMUM CLIMB OF 238 FT/NM TO 1800, OR STANDARD WITH MINIMUM CLIMB OF 272 FT/NM TO 1400, OR STANDARD AND CROSSING DER 42 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES WITH MINIMUM CLIMB OF 238 FT/NM TO 1800 OR 1900-3 FOR VCOA.
TEXTUAL DEPARTURE PROCEDURES:
RWY 8: CLIMB ON HEADING 090.00 AND ABC VOR/DME R-239 TO MIATA.
VISUAL CLIMB OVER AIRPORT:
RWY 8: OBTAIN ATC APPROVAL FOR VCOA WHEN REQUESTING IFR CLEARANCE. CLIMB IN VISUAL CONDITIONS TO CROSS PSTOL EASTBOUND AT OR ABOVE 5000, THEN ON LEX VOR/DME R-281 TO LEX.
TAKEOFF OBSTACLE NOTES:
RWY 8 LOW, CLOSE-IN OBSTACLES: TREES, VEHICLES, AND POLES BEGINNING 500 FT FROM DER EXTENDING TO 1/2 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 1546 MSL, 114 FT ABOVE DER. CROSSING DER 54 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 8 TAKEOFF MINIMUMS OBSTACLES: TREES AND TOWER BEGINNING 3/4 NM FROM DER EXTENDING TO 1.8 NM, RIGHT OF CENTERLINE, UP TO 2456 MSL, 265 FT ABOVE DER. CROSSING DER 42 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES.
Example 2: FAA Form 8260-15A: ODP with takeoff minimums obstacle penetration in ICA (no low, close-in obstacles noted) and obstacle penetration outside ICA. Highest CG outside ICA.
TAKEOFF MINIMUMS:
RWY 8: STANDARD WITH MINIMUM CLIMB OF 356 FT/NM TO 3500 OR 3400-3 FOR VCOA.
TEXTUAL DEPARTURE PROCEDURES:
RWY 8: CLIMBING LEFT TURN DIRECT ABC VOR/DME.
VISUAL CLIMB OVER AIRPORT:
RWY 8: OBTAIN ATC APPROVAL FOR VCOA WHEN REQUESTING IFR CLEARANCE. CLIMB IN VISUAL CONDITIONS TO CROSS PSTOL EASTBOUND AT OR ABOVE 5000, THEN ON LEX VOR/DME R-281 TO LEX.
Example 3: FAA Form 8260-15B (Graphic ODP), Obstacle penetration(s) inside/outside ICA (both low, close-in and takeoff obstacles). Highest CG within ICA.
DP ROUTE DESCRIPTION:
TAKEOFF RWY 18: CLIMB ON HEADING 185.22 TO 7700, THEN CLIMBING LEFT TURN DIRECT MKM VOR/DME, THEN ON MKM R-028 TO LARST, THENCE…
TAKEOFF RWY 36: CLIMB ON HEADING 005.22 TO 7100, THEN CLIMBING RIGHT TURN ON MKM R-028 TO LARST, THENCE…
VCOA ALL RWYS:
OBTAIN ATC APPROVAL FOR VCOA WHEN REQUESTING IFR CLEARANCE. CLIMB IN VISUAL CONDITIONS TO CROSS MKM VOR/DME NORTHEASTBOUND AT OR ABOVE 8100, THEN ON MKM R-028 TO LARST, THENCE…
… CROSS LARST AT OR ABOVE MEA/MCA FOR ROUTE OF FLIGHT.
TAKEOFF MINIMUMS:
RWY 8: 300-1 3/4 WITH MINIMUM CLIMB OF 238 FT/NM TO 1800, OR STANDARD WITH MINIMUM CLIMB OF 272 FT/NM TO 1400, OR STANDARD AND CROSSING DER 42 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES WITH MINIMUM CLIMB OF 238 FT/NM TO 1800 OR 1900-3 FOR VCOA.
TAKEOFF OBSTACLE NOTES:
RWY 8 LOW, CLOSE-IN OBSTACLES: TREES, VEHICLES, AND POLES BEGINNING 500 FT FROM DER EXTENDING TO 1/2 NM, LEFT, CROSSING AND RIGHT OF CENTERLINE, UP TO 1546 MSL, 114 FT ABOVE DER. CROSSING DER 54 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 8 TAKEOFF MINIMUMS OBSTACLES: TREES AND TOWER BEGINNING 3/4 NM FROM DER EXTENDING TO 1 1/2 NM, RIGHT OF CENTERLINE, UP TO 2456 MSL, 265 FT ABOVE DER. CROSSING DER 42 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES.
Example 4: FAA Form 8260-15B (SID), Obstacle penetration(s) inside/outside ICA (both low, close-in and takeoff obstacles).
DP ROUTE DESCRIPTION:
TAKEOFF RWY 18: CLIMB ON HEADING 185.22 TO 7700, THEN CLIMBING LEFT TURN DIRECT MKM VOR/DME, THEN ON MKM R-028 TO LARST, THENCE…
TAKEOFF RWY 36: CLIMB ON HEADING 005.22 TO 7100, THEN CLIMBING RIGHT TURN ON MKM R-028 TO LARST, THENCE…
TAKEOFF MINIMUMS:
RWY 18: 400-2 1/4 WITH MINIMUM CLIMB OF 259 FT/NM TO 1600, OR STANDARD WITH MINIMUM CLIMB OF 266 FT/NM TO 1500, OR STANDARD AND CROSSING DER 93 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES WITH MINIMUM CLIMB OF 259 FT/NM TO 1600.
RWY 36: 300-2 WITH MINIMUM CLIMB OF 210 FT/NM TO 1200, OR STANDARD WITH MINIMUM CLIMB OF 245 FT/NM TO 1200, OR STANDARD AND CROSSING DER 63 FT ABOVE DER ELEV CLEARS TAKEOFF MINIMUMS OBSTACLES WITH MINIMUM CLIMB OF 210 FT/NM TO 1200.
TAKEOFF OBSTACLE NOTES:
See FAA Form 8260-15A, Takeoff Minimums and Obstacle Departure Procedures (ODP).
g. When multiple runway entries are needed apply the following for takeoff obstacle notes:
(1) Both low, close-in and takeoff minimums obstacle(s) must be documented for each runway as applicable. All entries will be listed in numerical runway order from low to high and from left to right when the numerical runway designations match.
(2) Combine runways when the low, close-in and takeoff minimums obstacle notes are the exact same and when one or the other is not required. Do this in order from low to high and
2-1-3. ODP Documentation for Specific Design Combinations. › g. When multiple runway entries are needed apply the following for…
left to right in a single line when the numerical runway designator and the obstacle descriptions are the same.
Example: When both obstacle notes are available for all runways.
TAKEOFF OBSTACLE NOTES:
RWY 12L LOW, CLOSE-IN OBSTACLES: TREES BEGINNING 600 FT FROM DER, EXTENDING TO 1/2 NM, CROSSING CENTERLINE, UP TO 144 FT MSL, 89 FT ABOVE DER, CROSSING DER 49 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 12L TAKEOFF MINIMUMS OBSTACLES: BUILDINGS AND TOWER BEGINNING 1 1/2 NM FROM DER, EXTENDING TO 1 3/4 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 66 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
RWY 12R LOW, CLOSE-IN OBSTACLES: OBSTACLES 35 FT AND BELOW. CROSSING DER 15 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 12R TAKEOFF MINIMUMS OBSTACLES: BUILDINGS, CRANE, AND TOWER BEGINNING 1 1/2 NM FROM DER, EXTENDING TO 2 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 245 FT ABOVE DER, CROSSING DER 55 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
RWY 30L LOW, CLOSE-IN OBSTACLES: OBSTACLES 35 FT AND BELOW. CROSSING DER 15 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 30L TAKEOFF MINIMUMS OBSTACLES: BUILDINGS, CRANE, AND TOWER BEGINNING 1 1/4 NM FROM DER, EXTENDING TO 1 1/2 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 65 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
RWY 30R LOW CLOSE-IN OBSTACLES: OBSTACLES 35 FT AND BELOW. CROSSING DER 15 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 30R TAKEOFF MINIMUMS OBSTACLES: BUILDINGS, CRANE, AND TOWER BEGINNING 1 1/2 NM FROM DER, EXTENDING TO 1 3/4 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 65 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
Example: When both obstacle notes are not available for all runways: no low, close-in for one or more runways.
TAKEOFF OBSTACLE NOTES:
RWY 12L LOW, CLOSE-IN OBSTACLES: TREES BEGINNING 600 FT FROM DER, EXTENDING TO 1/2 NM, CROSSING CENTERLINE, UP TO 144 FT MSL, 89 FT ABOVE DER, CROSSING DER 49 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 12L TAKEOFF MINIMUMS OBSTACLES: BUILDINGS AND TOWER BEGINNING 1 1/4 NM FROM DER, EXTENDING TO 1 1/2 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 66 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
RWY 12R LOW CLOSE-IN OBSTACLES: OBSTACLES 35 FT AND BELOW. CROSSING DER 15 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 12R TAKEOFF MINIMUMS OBSTACLES: BUILDINGS, CRANE, AND TOWER BEGINNING 1 1/2 NM FROM DER, EXTENDING TO 2 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 245 FT ABOVE DER, CROSSING DER 55 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
RWY 30L TAKEOFF MINIMUMS OBSTACLES: BUILDINGS, CRANE, AND TOWER BEGINNING 1 1/4 NM FROM DER, EXTENDING TO 1 1/2 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 65 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
RWY 30R TAKEOFF MINIMUMS OBSTACLES: BUILDINGS, CRANE, AND TOWER BEGINNING 1 1/2 NM FROM DER, EXTENDING TO 1 3/4 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 65 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
Example: When both obstacle notes are not available for all runways: no takeoff min obstacles for one or more runways.
TAKEOFF OBSTACLE NOTES:
RWY 12L LOW, CLOSE-IN OBSTACLES: TREES BEGINNING 600 FT FROM DER, EXTENDING TO 1/2 NM, CROSSING CENTERLINE, UP TO 144 FT MSL, 89 FT ABOVE DER, CROSSING DER 49 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 12L TAKEOFF MINIMUMS OBSTACLES: BUILDINGS AND TOWER BEGINNING 1 1/4 NM FROM DER, EXTENDING TO 1 1/2 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 66 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
RWY 12R, 30L/R LOW, CLOSE-IN OBSTACLES: OBSTACLES 35 FT AND BELOW. CROSSING DER 15 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
Example: Both obstacle notes are not available for all runways: no takeoff min obstacles for some runways and no low, close-in for all runways.
TAKEOFF OBSTACLE NOTES:
RWY 30L TAKEOFF MINIMUMS OBSTACLES: BUILDINGS, CRANE, AND TOWER BEGINNING 1 1/4 NM FROM DER, EXTENDING TO 1 1/2 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 65 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
RWY 30R TAKEOFF MINIMUMS OBSTACLES: BUILDINGS, CRANE, AND TOWER BEGINNING 1 1/2 NM FROM DER, EXTENDING TO 1 3/4 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 65 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
Example: Combined notes. Only when the note is the exact same (Distances, heights/elevations, and positions)
TAKEOFF OBSTACLE NOTES:
RWY 12L/R LOW, CLOSE-IN OBSTACLES: OBSTACLES 35 FT AND BELOW. CROSSING DER 15 FT ABOVE DER ELEV CLEARS LOW, CLOSE-IN OBSTACLES.
RWY 30L/R TAKEOFF MINIMUMS OBSTACLES: BUILDINGS, CRANE, AND TOWER BEGINNING 1 1/2 NM FROM DER, EXTENDING TO 1 3/4 NM, LEFT, RIGHT, AND CROSSING CENTERLINE, UP TO 358 FT MSL, 297 FT ABOVE DER, CROSSING DER 65 FT ABOVE DER ELEV CLEARS TAKE-OFF MINIMUMS OBSTACLES.
Various Routed DP scenarios based on Order 8260.3.
Examples:
1. Straight DP Segments:
DR, No Turn (see Order 8260.3 figure below):
Figure 13-3-2
(ODP) RWY 09: CLIMB ON HEADING 090.00 TO 2000 BEFORE PROCEEDING ON COURSE.
(SID) RWY 09: CLIMB ON HEADING 090.00 FOR VECTORS TO ASSIGNED ROUTE.
Intercept PCG, Turn 15 Degrees or Less (see Order 8260.3 figures below):
Figure 13-3-3
(ODP) RWY 09: CLIMB ON I-ABC EAST COURSE TO 3000 BEFORE PROCEEDING ON COURSE.
(SID) RWY 09: CLIMB ON I-ABC EAST COURSE TO 3000 FOR VECTORS TO ASSIGNED ROUTE.
Figure 13-3-4, 13-3-5
(ODP)/(SID) RWY 36: CLIMB ON ABC VOR R-010...
Figure 13-3-6
(ODP) RWY 36: CLIMB ON ABC R-190 TO ABC VOR BEFORE PROCEEDING ON COURSE.
(SID) RWY 36: CLIMB ON ABC R-190 TO CROSS ABC VOR AT 5000.
2. Turning DP Segments:
DR to Intercept PCG Radial or Bearing, Turn Greater Than 15 Degrees (see Order 8260.3 figures below):
Figure 13-3-7
(ODP)/(SID) RWY 36: CLIMBING LEFT TURN HEADING 330.00 AND ABC VOR R-180…
Figure 13-3-8
(ODP)/(SID) RWY 36: CLIMBING RIGHT TURN HEADING 040.00 AND ABC VOR R-010…
Figure 13-3-9
(ODP)/(SID) RWY 36: CLIMB ON ABC VOR R-030 TO…
Figure 13-3-10
(ODP)/(SID) RWY 36: CLIMB ON ABC VOR R-220 TO ABC VOR ...
Figure 13-3-11
(ODP)/(SID) RWY 36: CLIMB ON HEADING 360.00 TO CROSS ABC VOR R- 220, THEN RIGHT TURN HEADING 070.00 AND ABC VOR R-220…
2-1-4. Standard Instrument Departures. › b. When a SID is designed to incorporate radar vectors or a course to…
Direct to Facility, Turn 15 Degrees but Less Than or Equal to 90 Degrees and Direct to Facility, Turn 15 Degrees but Less Than or Equal to 180 Degrees (see Order 8260.3 figures below):
Figures 13-3-12 and 13-3-13
(ODP)/(SID) RWY 36: CLIMBING RIGHT TURN DIRECT ABC VOR…
3. Multiple PCG Turn Segments:
See Order 8260.3 figures below:
Figure 13-3-17
(ODP)/(SID) RWY 36: CLIMB ON ABC VOR R-195 TO ABC VOR, THEN RIGHT TURN ON XYZ VOR R-255 TO XYZ VOR…
Figure 13-3-18
(ODP)/(SID) RWY 36: CLIMB ON ABC VOR R-010 TO ALPHA, THEN RIGHT TURN ON XYZ VOR R-240 TO XYZ VOR…
Figure 13-3-19
(ODP)/(SID) RWY 36: CLIMB ON ABC VOR R-195 TO XYZ VOR, THEN RIGHT TURN ON XYZ VOR R-075 TO BRAVO…
2-1-4. Standard Instrument Departures. Design 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 the SID is part of an IFR, ATC clearance. The following rules apply to SIDs:
a. 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.
b. 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.
2-1-5. Design Constraints. The following design constraints apply to all ODPs and SIDs:
a. DPs must not require a turn prior to reaching 400 feet above the DER elevation. See Order 8260.3 and Order 8260.58 when a turn is required within 2 NM of DER.
b. The FPAG (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-5.h.(3) for additional information regarding establishing/publishing greater than standard CGs.
2-1-5. Design Constraints. › c. Specify speed restrictions only when necessary to ensure obstacle…
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.
(1) 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 CG values.
(2) When the FPAG will not approve a CG in excess of 500 ft/NM (600 ft/NM for helicopters) and all of the obstacles forcing such a CG are located inside the ICA (extended) 3 SM or less from DER, a ceiling and visibility may be applied to see and avoid the obstruction(s) as the only option available.
(3) When the FPAG will not approve a CG in excess of 500 ft/NM (600 ft/NM for helicopters) and any of the obstacles forcing such a CG are located outside the ICA (extended) greater than 3 SM from DER; a stand-alone VCOA procedure may be used as the only option available for obstacle avoidance.
c. Specify speed restrictions only when necessary to ensure obstacle clearance, airspace efficiency during turns, or when necessary to achieve an operational advantage. Refer to applicable DP criteria directives.
(1) Speed restrictions to support ATC requirements are only allowed in SID design and must not be included in ODPs.
(2) 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.
(3) Speed restrictions may apply to the entire procedure or to a specific point-in-space. 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.”
(4) 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).
(5) Do not chart minimum or mandatory speed restrictions in excess of 250 KIAS below 10,000 feet MSL.
d. Do not use fan markers as a fix to designate a turning point on a SID or ODP.
e. Do not establish VCOA procedures in conjunction with a SID.
f. Except for departures that use Radar vectors to join RNAV routes, RNAV DPs must only serve one airport.
2-1-5. Design Constraints. › h. Charting constraints.
g. 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 (jet, turboprop, etc.) or different equipment requirements (distance measuring equipment (DME), non-DME). When this is necessary, design separate procedures.
h. 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 DPs may require depiction of a minimum altitude at a fix established along the departure route. SIDs may require altitudes to support ATC requirements; however, do not depict ATC-required altitudes on ODPs.
(b) When ATC requests a minimum “at or above” altitude restriction at a fix in an initial SID routing (prior to reaching the SID termination fix) that is higher than the required procedure design minimum altitude at the same fix, the higher requested ATC altitude then becomes the minimum altitude at that fix. This altitude must support all procedure design and criteria requirements [i.e., obstacle clearance/procedure design constraints/navigation solution and the ATC requirement(s)].
1. When establishing crossing altitudes for other than meeting obstacle clearance and/or to support a shortened ICA to ensure 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. FPAG’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 13, 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-5.h.(2)(b)].
(d) Enter altitudes to be charted on the appropriate FAA Form 8260-15 series (see appendix D or appendix E). Government and civil charting organizations will chart/depict these altitudes according to their individual specifications.
(e) For SIDs, top altitudes must be documented on FAA Form 8260-15B, Graphic Departure Procedure.
1. Top Altitudes will be provided by the applicable controlling ATC Facility or the Service Area Flight Procedures Team (FPT) using the Graphic DP Requirements Worksheet per appendix B.
2. 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 (do not exceed three per procedure).
3. A top altitude may be specified in various combinations (the variations permitted are specified in appendix D, section 2, and appendix E, section 1).
a A specific altitude or flight level
b ATC may elect to not publish a specific numerical top altitude, preferring to issue the top altitude as part of the ATC clearance (to assist ATC when flexibility is needed for the efficient flow of traffic). 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 (DRD). When ATC requests a top altitude of “AS ASSIGNED BY ATC” the lowest numerical maintain altitude that ATC would assign must be provided on the Graphic DP Requirements Worksheet. This altitude will be used for evaluation purposes.
c Various top altitude combinations must not be combined using “OR” because ATC always has the authority to change an altitude assignment (i.e., “CHART TOP ALTITUDE: 7000 OR AS ASSIGNED BY ATC” or “CHART TOP ALTITUDE: 7000 OR PROPS 5000”).
d It may be in the form of two different altitudes used to support different aircraft types (jet or propeller driven aircraft).
4. Top altitudes 18,000 feet MSL and above must be specified as a Flight Level.
5. 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 gradient termination altitude listed in the takeoff requirements of the procedure. For example, if the takeoff minimums state a 360 ft/NM CG until reaching 6000, the ATC assigned top altitude will be no lower than 6000.
(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 FAA Form 8260-15 series (see appendix D, appendix E, appendix F, or appendix G).
(a) Establish a single minimum CG exceeding 200 ft/NM (400 ft/NM for helicopters beginning at the IDF) whenever required for obstruction clearance and include the altitude to which the gradient is required in the Takeoff Minimums note; e.g., “(TAKEOFF MINIMUMS) WITH MINIMUM CLIMB OF 300 FT/NM TO 4300.”
(b) When a CG is necessary to support a shortened ICA to ensure 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 establish a greater than standard CG solely to reach an altitude sooner for LNAV engagement purposes when an early turn is not necessary [see Order 8260.58, paragraph 5-1-1.c.(2)].
(d) 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-5.h.(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 CG 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-5.c. 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 FAA 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.”
(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 FAA Form 8260-15B. U.S. Government charts will include this immediately following the procedure title; e.g., TETON ONE DEPARTURE (OBSTACLE).
2-1-5. Design Constraints. › i. PBN chart annotation.
(6) ODPs designed 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 FAA 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 CGs on the graphic chart. Obstacle DPs must also include obstacle note data, as applicable (see paragraph 2-1-3) on the graphic chart.
(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 FAA Form 8260-15B, use: “CHART: NOTE: DO NOT FILE – TO BE ASSIGNED BY ATC.”
i. PBN chart annotation. A navigation specification (NavSpec) contains the performancebased 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, and RNP 0.3. NavSpecs is detailed in Order 8260.58. SID transitions are an en route flight phase, refer to Order 8260.58 Table 1-2-1, En Route Domestic.
(1) Provide a PBN Requirements Box when there is a PBN segment in the procedure.
(2) Separate the PBN Requirements Box from other procedural and non-procedural notes and information on the chart.
(3) Specify PBN requirements notes on FAA 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.”).
(a) NavSpec: Identify the NavSpec as appropriate. RNAV 1, RNP 1, A-RNP, RNP AR DP, RNP 0.3. RNP AR DP (without additional NavSpecs) can only be used when publishing a stand-alone graphic DP. 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.”).
(b) Sensor: The required sensor is applicable to the NavSpec.
1. RNAV 1: Aircraft equipped with GPS and/or DME/DME/IRU sensors may support RNAV 1 DPs. If the RNAV DP intends to support aircraft without GPS, then the
DP requires a DME availability or screening assessment to ensure adequate DME facility coverage exists along the DP’s path. If the DME assessment is satisfactory and radar monitoring is also available, then the PBN Requirements Box may identify both GPS and DME/DME/IRU as supporting sensors. If the DME assessment fails or radar monitoring is not available, then the RNAV 1 DP must identify GPS as the only available sensor.
2. RNP 1, A-RNP, RNP AR DP, and RNP 0.3: The only authorized sensor for any RNP NavSpec is GPS. No ATC monitoring is required when GPS is the only sensor option (do not annotate “RADAR REQUIRED”).
(c) Function: Common functions are RF turns and MIN RNP values. These functions can only be used with RNP NavSpecs. They can be applicable to the entire DP or only to a specific runway transition(s) or leg(s).
1. 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.”).
2. 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.”).
3. Lateral Accuracy Function: A-RNP has lateral accuracy values of 1.00 or 0.30. RNP AR DP has lateral accuracy 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”).
(d) 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.
1. A-RNP require AP/FD; document “AP/FD” as a remark.
2. RNP 0.3 require AP; document “AP” as a remark.
3. RNP AR DP require authorization; document “AUTHORIZATION REQUIRED” as a remark.
4. 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.”).
5. 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”).
6. 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”).
(e) Common PBN requirements notes(s) as applicable:
1. 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.”
2. RNAV 1 (with specific RF turns): “RNAV 1 – DME/DME/IRU OR GPS. FROM HEERE OR THERE: RNP 1 – GPS, RF.”
3. RNP 1 no RF turns: “RNP 1 – GPS.”
4. RNP 1 (with RF turns or specific RF turns): “RNP 1 – GPS, RF.” or “RNP 1 – GPS. FROM HEERE OR THERE: RF.”
5. A–RNP (lateral accuracy of 1.00 and no RF turns): “A-RNP – GPS, AP/FD.”
6. A–RNP (lateral accuracy of 0.30 and no RF turns): “A-RNP – GPS, MIN RNP 0.30, AP/FD.”
7. 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.”
8. RNP AR DP (lateral accuracy of 1.00 and no RF turns): “RNP AR DP – GPS, AUTHORIZATION REQUIRED.”
9. RNP AR DP (lateral accuracy < 1.00 and no RF turns): “RNP AR DP – GPS, MIN RNP 0.70. AUTHORIZATION REQUIRED.”
10. 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.”
11. Helicopter RNP 0.3: “RNP 0.3 – GPS. AP.” or “RNP 0.3 – GPS, RF. AP.”
j. 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., non-directional 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 DR navigation.
2-1-5. Design Constraints. › k. Terminology.
(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.
(a) A note may be required to address the need for specific distance measuring equipment (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.”
(b) Except as required by paragraph 2-1-5.i.(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.”
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.
(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.
k. Terminology. The following terminology applies for the 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 designers 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…”
(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) For a graphic DP ensure initial departure instructions that require altitude restrictions are written clearly and in order to be flown to lessen the possibility of pilot
2-1-5. Design Constraints. › m. Attention All Users Page (AAUP).
deviations. For example, “CLIMB ON HEADING 240.15 MAINTAIN 1500, THEN TURN RIGHT HEADING 280 AND CROSS TEB 4.5 DME AT 1500, THEN MAINTAIN 2000, THENCE…” or “CLIMB ON HEADING 195.47 TO 1500, THEN CLIMBING RIGHT TURN 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 DP requiring a turn does not require an initial climb heading to be specified if less than 15 degrees for example, “CLIMB DIRECT XYZ VOR… or CLIMB ON XYZ VOR R- 226…”
(7) Direction of turn must be specified when the turn exceeds 15 degrees for example, “CLIMBING RIGHT TURN DIRECT XYZ VOR… or CLIMBING RIGHT TURN ON XYZ VOR R-226… ”
(8) Do not use the word immediate/immediately in any type of departure instructions; e.g., turning instruction or speed restrictions. Old early turn DPs may contain instructions to “Turn left (right) as soon as practicable.” This terminology is used on non-standard DPs approved by the Flight Standards or the appropriate military authority. When an intercept heading is defined (see Order 8260.3, paragraph 13-3-3) it must be charted.
l. 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 design. See appendix G of this order for documenting the design of a DVA.
m. 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 2.q.(3).
(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 Air Traffic.
(b) Responsible for the design, among other things, of an AAUP.
(2) AAUP preparation. The AAUP must present the step-by-step procedures used to conduct the procedure. Document the AAUP using FAA Form 8260-15E, Attention All Users Page, and the guidance provided in appendix E, section 3.
Section 2-1. DP Guidelines › 2-1-6. Responsibilities.
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 documentation guideline. AAUPs must reflect the requirements of the specific procedure and airport for which they are designed.
(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. 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, FPAG 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.
(c) 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 required.
(d) Publish the AAUP in the National Flight Data Digest (NFDD).
(e) The NFDD is the source for AAUP information for publication by all chart producers.
2-1-6. Responsibilities.
a. General. The following guidance outlines procedures for DP requests, processing, and cancellation:
(1) Procedure requests. SIDs are normally requested by the ATC facility responsible for departure control at the airport where the procedure is proposed, or by another proponent 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 IFP Validation Team in accordance with Order 8260.43, Flight Procedures Management Program.
2-1-6. Responsibilities. › c. ATC.
(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, FPAG, and other Air Traffic 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 FAA Form 8260-15D, Diverse Vector Area, is no longer valid.
b. Proponent. A proponent’s request to design or amend 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 design. 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 design assistance from the servicing ATC facility.
(4) Air Traffic is responsible for satisfying the Safety Risk Management requirements from Order 1100.161, Air Traffic Safety Oversight, for changes to the National Airspace System (NAS).
(5) New DP design or amendment requests must specify which ICA criteria and design guidance to use for DPs.
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, miscellaneous activity areas, etc.
Note: When an ATC facility proposes SID design 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.
2-1-6. Responsibilities. › d. Service Area Operations Support Group.
(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 FAA 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/amendment of an AAUP is necessary for RNAV DPs. See paragraph 2-1-5.m. 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.
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.
2-1-6. Responsibilities. › e. Aeronautical Information Services.
(7) Provide one copy of each FAA Form 8260-2 and 8260-15 series FAA 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.
e. Aeronautical Information Services.
(1) Develop and process textual ODPs on FAA Form 8260-15A under applicable directives.
(2) Develop and process graphic ODPs and SIDs on FAA Form 8260-15B.
(3) Develop and process an FAA Form 8260-15C, Departure Data Record, for all RNAV DPs.
(4) Develop and process an FAA Form 8260-15D for all DVAs.
(5) Ensure that a DME/DME screening model has been run on graphic RNAV ODPs (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 FAA Form 8260-2s and original 8260-15 series FAA Forms to Aeronautical Data Group. Ensure copies are available for distribution [see paragraph 2-1-6.d.(5) and 2-1-6.d.(7)].
(8) Develop, review, track, and cancel Notice to Air Missions (NOTAMs) relating to ODPs, SIDs, and 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.
(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.
2-1-6. Responsibilities. › f. Flight Program Operations.
(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 FAA Form 8260-15A for the airport accordingly.
(15) When it is necessary to cancel a DP, process the appropriate FAA Form 8260-15 as directed in paragraph 2-1-9.c.
(16) Add the “T” symbol to the IAP and SID charts whenever FAA 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 FAA 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 FAA 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
(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-5.m.(4) for more specific AAUP responsibilities.
2-1-8. Military DPs. › b. The FAA requires that all military DPs be coordinated with FAA ATC…
(3) Resolve data conflicts, form discrepancies, etc., with Aeronautical Information Services.
(4) File and maintain the original signed copy of the forms.
2-1-7. Accuracy Verification and Responsibilities. Any ATC facility, military service, 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-8. Military DPs.
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 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 Group.
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.
2-1-9. FAA 8260-15 Series Forms. › a. The 8260-15 series FAA forms document standard takeoff minimums and…
d. When a military DP has a CG 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-9. FAA 8260-15 Series Forms (see appendices D through G).
a. The 8260-15 series FAA forms document standard takeoff minimums and facilitate transmittal of nonstandard takeoff minimums and/or DPs. These forms will be the basis for charting agencies to publish non-standard takeoff minimums, DPs, and/or to add/delete charting icons used to denote that other than standard takeoff minimums and/or specific ODPs are published. For helicopter departures, see appendix F.
(1) Use FAA Form 8260-15A to document:
(a) Standard takeoff minimums,
(b) Nonstandard takeoff minimums and/or higher than standard CGs for a runway,
(c) Textual ODPs,
(d) That the ODP for a runway is published graphically, and
(e) Other pertinent textual data for publication; e.g., obstacle data notes, VCOA data, etc.
(2) Use FAA Form 8260-15B to document:
(a) Graphically depicted complex ODPs and all SIDs, and
(b) Other pertinent procedural data; e.g., fixes, NAVAIDs, routes, vectoring areas, altitudes, etc. required for charting database development on RNAV DPs.
(3) Use FAA Form 8260-15C to document RNAV DPs in a manner consistent with and which aids in charting and database coding. Specifically use FAA 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, and
(b) Altitude and airspeed restrictions associated with fixes.
(4) Use FAA Form 8260-15D to document a DVA.
(5) Use FAA 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-5.m. for AAUP guidance.
b. Administratively process the 8260-15 series FAA 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 CG approval, submit
2-1-11. Procedure Amendments. › a. General Information.
documentation showing calculations. See Order 8260.19, chapter 2, for waiver and approval processing guidance.
c. Cancel FAA 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 FAA Form 8260-15A/B/D and into the corresponding blocks on blank FAA Form 8260-15A and/or FAA Form 8260-15B/8260-15D. Additionally, on FAA 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 FAA Form 8260-15A and/or “DP Route Description” section of FAA 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-10. Periodic Review. Follow Order 8260.19 for periodic review requirements in addition to the following:
a. When reviewing DPs, ensure all DPs for an airport use the same ICA criteria.
b. Add a note to the periodic review documentation which ICA was used for the review (see paragraph 2-1-1.i. for examples).
2-1-11. Procedure Amendments. Amend all DPs using either the full amendment or an abbreviated amendment process as specified below.
a. General Information. 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 may be completed using the legacy ICA as long as all DPs for the airport use the legacy ICA.
(1) A full amendment requires a complete procedure package (i.e., all necessary forms, maps, and supporting documentation) be developed and submitted for processing.
(2) An abbreviated amendment only requires submission of FAA Forms 8260-15A or 8260-15B as applicable (and FAA Form 8260-15C, if an RNAV procedure) for processing. 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. Apply Order JO 8200.44, Flight Inspection Services Instrument Flight Procedure Coordination, when determining what must be submitted for flight inspection.
(3) Submit DPs designed by a non-FAA Service Provider to the FPAG to determine flight validation requirements.
(4) Flight Program Operations (or the FPAG for procedures not developed and/or flight inspected by the FAA) may establish unique/specific policy guidelines with individual procedure
2-1-11. Procedure Amendments. › c. Graphic ODPs and SIDs.
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 FPAG a copy of all policy memorandums between Flight Program Operations and procedure developers.
(5) Paragraphs 2-1-1.f, 2-1-1.g, and 2-1-1.h apply when amending DPs.
b. Textual ODPs.
(1) When completing a full amendment, advance the amendment number in the “AMDT No.” item of FAA 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).
c. Graphic ODPs and SIDs.
(1) Whenever changing the “DP Name” in the title line of FAA 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 FAA 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).
(d) When not using the legacy ICA criteria in Orders 8260.3/8260.46.
(4) Use an abbreviated amendment whenever a change is made to the items listed below as specified on FAA 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. An abbreviated amendment is only allowed when using the legacy ICA criteria and changes to takeoff minimums or takeoff obstacle notes are needed.
2-1-11. Procedure Amendments. › d. DVA.
(a) Transition routes (only when removing).
(b) Procedural data notes/Takeoff minimums (legacy ICA only).
(c) Takeoff obstacle notes (legacy ICA only).
(d) Lost Comm procedures.
(e) Additional flight data.
(f) Airports served (only when an airport ID, city/state has changed or an airport is deleted).
(g) Communications.
(h) Fixes and/or NAVAIDs (only those requested for charting purposes but are not included in the textual description of the departure or entered in the transition route data).
(i) Remarks (that will require a change to what will be charted on the procedure).
(j) Altitude changes (RNAV procedures require 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 (MV) 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 FAA 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).
d. DVA. Any change to a DVA is considered an amendment and requires a new FAA Form 8260-15D to be generated, establishing a new amendment number.
3-1-1. General. › j. A transition may be developed from the end of a SID to support a…
Chapter 3. Graphic Instrument Departure Procedures (DPs)
Section 3-1. General Guidance
3-1-1. General.
a. DPs must be designed so that they provide obstacle clearance, least onerous routing (where possible), and can be confidently and consistently flown by all aircraft expected to use the procedure.
b. A DP must be relatively simple and easily understood. To avoid chart complexity and human factors concerns, limit the number of airports and/or runways from which a particular DP may be used to only those necessary to support operations.
c. A DP should use only the minimum number of fixes, turns, or altitude changes necessary to depict the route.
d. A DP should be developed to accommodate as many different types of aircraft as possible.
e. A DP should avoid the use of DME arcs.
f. Graphic ODPs must be designed to terminate at a fix/NAVAID located within the IFR en route structure or at an altitude that will allow random IFR flight.
g. A SID must provide for a significant user/system benefit.
h. A SID must reduce pilot/controller communications and workload.
i. A SID must be designed to terminate at a fix/NAVAID located within the IFR en route structure, at an altitude that will allow random IFR flight, or at a position where ATC radar service is provided.
j. A transition may be developed from the end of a SID to support a need to take aircraft to additional fixes/NAVAIDs depicted on an IFR en route chart. A SID may contain multiple transitions and may share a common segment prior to branching off into multiple directions.
(1) 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 IFR altitude (MEA) for the route [see paragraph 2-1-5.h.(2)(b)1]. Do not raise an MEA to support ATC operational requirements; use fix crossing altitudes where operationally needed.
(2) MEAs and minimum obstruction clearance altitudes (MOCAs) are required for all transitions as follows:
(a) Each MEA along the transition route (including FL 180 and above) must be documented on appropriate 8260-series FAA forms. By definition, the MEA also encompasses
3-1-1. General. › l. Altitude
the minimum reception altitude (MRA). If transitions share a common segment, make sure the MEA for that segment is the same for each transition.
(b) Each MOCA along the transition route must be documented on appropriate 8260-series FAA forms. To reduce chart clutter, do not chart MOCAs less than 500 feet below MEAs. Document MOCAs that are not to be charted when less than 500 feet below MEAs in the remarks section of the appropriate 8260-series FAA forms.
Example:
“REMARKS: DO NOT CHART MOCA: FROM MICKY TO TWN VORTAC, TWN VORTAC TO WSN VORTAC.”
k. Avoid speed restrictions whenever possible. See paragraphs 2-1-5.c. and 2-1-5.h.(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-5.h.(2) for specific guidance and charting constraints.
(3) Do not use multiple altitude restrictions at the same fix for different aircraft types or departure runways; e.g., “Turboprops cross GRAVY at-or-below 5000, Turbojets 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 FAA Form 8260-15B (see also paragraph 2-1-5.h.(2)(e) and appendix D, section 2, or appendix E, section 1, for the top altitude variations permitted).
m. CG. DPs are designed assuming a minimum standard CG of 200 ft/NM (400 ft/NM for helicopters) to ensure required obstacle clearance is achieved.
(1) Higher CGs must be published when required for obstruction clearance and/or when needed to support a shortened ICA for LNAV engagement (see paragraphs 2-1-5, 2-1-5.h.(3)(c), and Order 8260.58 paragraph 5-1-1.c.(2) for specific guidance).
3-1-2. Minimum Safe Altitude (MSA). › b. When a Omni-directional facility is the specified point.
(2) Do not establish a greater than standard CG solely to reach an altitude sooner for LNAV engagement purposes when an early turn to support an RNAV leg is not necessary [see Order 8260.58 paragraph 5-1-1.c.(2)]. When this is needed (to support a radar vector segment) it is considered an ATC CG.
3-1-2. Minimum Safe Altitude (MSA). Graphic DP documentation must include MSA information for each airport served by the DP. Document the specified point the MSA is centered on followed by the sectors, when defined, and the altitude(s).
a. If the DP serves more than one airport:
(1) Precede the MSA information with the airport ID (see paragraph 2-1-1.j.) unless the specified point is the airport reference point (ARP).
(2) When all MSAs are defined by the same Omni-directional facility or use the ARP and all use the same altitude and sectors, when applicable, precede the MSA information with “ALL AIRPORTS” (see applicable examples below).
b. When a Omni-directional facility is the specified point:
(1) Enter the identification and type of facility.
Example:
Single airport: “XYZ VORTAC, 3700”
Example:
Multiple airports: “MDW: XYZ VORTAC, 3700; ORD: LMN VORTAC, 3500” or “ZZZ/PYYY: ABC NDB, 4000; WWW/PVVV: CDE VOR/DME, 3000” or “ALL AIRPORTS: XYZ VORTAC, 3700”
(2) If the omni-directional facility MSA is sectored, enter the information clockwise by sectors referenced to bearings from the omni-directional facility for charting.
Example:
Single airport: “XYZ VORTAC 360 CW 170, 4900; 170 CW 360, 3700”
Example:
Multiple airports: “MDW: XYZ VORTAC 360 CW 170, 4900 and 170 CW 360, 3700; ORD: XYZ VORTAC 360 CW 170, 4900 and 170 CW 360, 3700” or “ALL AIRPORTS: XYZ VORTAC 360 CW 170, 4900 and 170 CW 360, 3700”
(3) When the facility-to-airport distance exceeds 25 NM as defined in Order 8260.3 enter the distance in NM as follows:
3-1-3 Naming of DPs. › f. Number each original graphic DP “ONE.”
Example:
“XYZ VORTAC, 3700 (28 NM)”
c. When the ARP is the specified point use the airport ID.
Example:
Single airport: “XXX, 4000” or “AAA/PBBB, 4000”
Example:
Multiple airports: “XXX, 3700; VVV, 3500” or “ALL AIRPORTS: 3700” or “AAA/PBBB, 4000; BBB/PCCC, 8000”
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.
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-1.k. for the amendment process).
3-1-6. RNAV DPs. › a. Waypoints.
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 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 three-letter ID, 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 ID 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.
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
3-1-6. RNAV DPs. › b. Leg types.
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. If the aircraft is climbing straight ahead there is no requirement to publish an engagement altitude [see paragraph 2-1-5.h.(3)(c) and Order 8260.58, paragraph 5-1-1.c.(2)].
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 to the DP termination fix; must be 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.
Continue reading ↓ 120 of 244 passages shown