Departure Procedures

Departure procedures provide a safe and expeditious climb out from an airport to the appropriate enroute structure.

Departure Procedures

Introduction to Departure Procedures

Help Us Grow

Enjoy CFI Notebook? A one-time donation helps us create more high-quality lessons, quizzes, scenarios, graphics, and interactive tools.

One-Time Donation
Departure Procedures

Departure Procedures Key Highlights

  • Departure procedures provide standardized IFR routing and obstacle clearance guidance during the initial (departure) phase of flight.
  • Published departure procedures improve terrain avoidance, traffic flow management, and communication efficiency.
  • Obstacle Departure Procedures (ODPs) are designed primarily to ensure obstacle clearance after takeoff.
  • Standard Instrument Departures (SIDs) provide ATC-assigned routing that enhances traffic sequencing and operational efficiency.
  • Pilots are responsible for reviewing departure procedures during preflight planning and determining aircraft performance capability.
  • Departure procedures may include altitude restrictions, heading assignments, climb gradients, and navigation requirements.
  • Aircraft unable to meet published climb gradients or performance requirements may require alternate routing or operational planning.
  • ATC clearance does not relieve pilots of responsibility for obstacle clearance unless radar vectors are specifically assigned.
  • Proper departure briefings improve situational awareness, workload management, and cockpit coordination during critical flight phases.
  • Understanding departure procedures improves IFR operational safety, terrain avoidance, and regulatory compliance.
Departure Procedures

Departure Procedure Development/Criteria

  • Departure Procedure Decision Flowchart
    Departure Procedure Decision Flowchart
  • Diverse Departure Obstacle Assessment
    Diverse Departure Obstacle Assessment
  • Departure Procedure Development:

    • As part of the instrument-procedure development process, the FAA evaluates runways to determine whether a departure procedure (DP) or other departure restrictions are required. []
      • If there is a need to better manage air traffic, a Standard Instrument Departure (SID) may be published.
      • However, if an obstacle penetrates what is called the 40:1 obstacle identification surface, then the procedure designer chooses whether to: []
        • Establish a steeper-than-normal climb gradient (greater than 200 feet per nautical mile (FPNM));
        • Establish a steeper-than-normal climb gradient with an alternative that increases takeoff minima to allow the pilot to remain clear of the obstacle(s) visually;
        • Design and publish a specific departure route; or
        • A combination or all of the above.
      • If an aircraft may turn in any direction from a runway within the limits of the assessment area and remain clear of obstacles.
        • In that case, that runway passes what is called a diverse departure assessment, and no ODP will be published.
  • Departure Procedure Decision Flowchart
    Departure Procedure Decision Flowchart
  • Departure Procedure Assessment Criteria:

    • Unless specified otherwise, required obstacle clearance for all departures, including diverse, is based on:
      • The pilot is crossing the departure end of the runway at least 35 feet above the departure end of the runway elevation.
      • The pilot is climbing to 400 feet above the departure end of the runway before making the initial turn.
      • The pilot maintains a minimum climb gradient of 200 FPNM unless required to level off due to a crossing restriction until reaching the minimum IFR altitude.
      • The assumption of normal aircraft performance, and that all engines are operating.
        • The operator is responsible for developing contingency procedures for an engine failure or other emergency after liftoff.
    • Read and comply with all notes/ATC instructions regarding the departure procedure, as not every location is alike.
  • Departure Procedure Mitigation:

    • Initial Turn to Clear Obstacles
      Initial Turn to Clear Obstacles
    • DPs (or ATC) may specify an initial turn to clear obstacles:
      • For Example: ATC: "Climb [Heading] to [Altitude] before turning right." []
    • Initial Turn to Clear Obstacles
      Initial Turn to Clear Obstacles
    • Initial Climb Gradient
      Initial Climb Gradient
    • DPs (or ATC) may specify (as takeoff minimums) a greater climb gradient to clear obstacles: []
      • For Example: ATC: "Minimum climb 340 FPNM to ALPHA."
    • Initial Climb Gradient
      Initial Climb Gradient
    • Crossing Altitude Restriction
      Crossing Altitude Restriction
    • DPs (or ATC) may specify a fix with a minimum and/or maximum crossing altitudes that must be adhered to before passing the fix: []
      • If a turn is specified at a fix, the turn must be made at that fix.
      • For Example: ATC: "Cross ALPHA intersection at or above 4,000'; maintain 6,000'."
    • Crossing Altitude Restriction
      Crossing Altitude Restriction
    • An obstacle on the extended runway centerline may require an early turn:
      • The published departure instructions will include the language "turn [left/right] as soon as practicable" though "practical" or "feasible" may exist in some existing departure text.
      • These departures include a ceiling minimum of at least 300 feet and a visibility minimum of at least 1 statute mile.
      • For Example: ATC: "turn left as soon as practicable."
    • Diverse Departure Obstacle Assessment
      Diverse Departure Obstacle Assessment
    • Note that compliance with climb gradients is mandatory when the procedure is part of the ATC clearance.
      • An exception applies when increased takeoff minimums are provided and weather conditions allow compliance with those minimums.
    • The 40:1 obstacle identification surface (OIS) begins at the departure end of runway (DER) and slopes upward at 152 FPNM until reaching the minimum IFR altitude or entering the en route structure. This assessment area is normally limited to:
      • 25 nautical miles (NM) from the airport in non-mountainous areas and 46 NM in designated mountainous areas.
      • Beyond this distance, the pilot is responsible for obstacle clearance if not operating on a published route, if below (having not reached) the MEA (Minimum En Route Altitude) or MOCA (minimum obstruction clearance altitude) of a published route, or an ATC-assigned altitude.
      • ODPs are generally designed to terminate within these distance limitations. However, some ODPs contain routes that exceed 25/46 NM.
        • These routes provide obstacle protection through the end of the ODP.
    • Obstacles that are located within 1 NM of the DER and penetrate the 40:1 OCS are referred to as "low, close-in obstacles."
    • The standard required obstacle clearance (ROC) of 48 feet per NM to clear these obstacles would necessitate a climb gradient exceeding 200 feet per NM for a very short distance, only until the aircraft was 200 feet above the DER.
    • To eliminate publishing an excessive climb gradient, the obstacle AGL/MSL height and location relative to the DER is noted in the "Take-off Minimums and (OBSTACLE) Departure Procedures" section of a given Terminal Procedures Publication (TPP) booklet.
      • The purpose of this note is to identify the obstacle(s) and alert the pilot to the height and location of the obstacle(s).
      • Compliance with 14 CFR Part 121 or 135 one-engine-inoperative (OEI) departure performance requirements, or similar ICAO/State rules, cannot be assured by the sole use of takeoff obstacle note data as published in the TPP.
      • Operators should refer to precise data sources (for example, GIS (Geographic Information System) database, etc.) specifically intended for OEI departure planning for those operations.
    • Climb gradients greater than 200 FPNM are specified when required to support procedure design constraints, obstacle clearance, and/or airspace restrictions.
      • When ATC includes the procedure in a clearance, pilots must comply with the climb gradient for that purpose unless provided with increased takeoff minimums, and the weather conditions allow compliance with those minimums.
      • "Cross ALPHA intersection at or below 4000; maintain 6000." The pilot climbs at least 200 FPNM to 6000. If reaching 4000 before ALPHA, the pilot levels off at 4000 until passing ALPHA; then immediately resumes at least 200 FPNM climb.
      • "TAKEOFF MINIMUMS: RWY 27, Standard with a minimum climb of 280' per NM to 2500."
      • A climb of at least 280 FPNM is required to 2500 and is mandatory when receiving a departure procedure in the ATC clearance.
      • Some SIDs continue to publish climb gradients labeled “ATC.” These gradients support an ATC altitude restriction and may not be required for obstacle clearance or procedure design.
        • The FAA revises SIDs as part of the standard procedure-amendment process.
    • Procedures may specify climb gradients only to an altitude/fix, above which the normal gradient applies.
      • An ATC-required altitude restriction published at a fix will not have an associated climb gradient published with that restriction. Pilots must determine if crossing altitudes can be met, based on the performance capability of the aircraft they are operating.
      • "Minimum climb 340 FPNM to ALPHA."
      • The pilot climbs at least 340 FPNM to ALPHA, then at least 200 FPNM to MIA.
Departure Procedures

Terminal Instrument Procedures

  • DRAKE TWO (OBSTACLE) (RNAV)
    DRAKE TWO (OBSTACLE) (RNAV)
  • STAAV EIGHT DEPARTURE (RNAV)
    STAAV EIGHT DEPARTURE (RNAV)
  • Instrument Flying Handbook, ODPs and SIDs
    Instrument Flying Handbook, ODPs and SIDs
  • There are multiple ways to define a safe area from the runway up to the airway/enroute structure.
  • DPs may be designed using either conventional or RNAV criteria.
  • Pilot Navigation Departure:

    • Consists of pre-published routes that supply headings, altitudes, and reporting points for the transition from takeoff to the enroute structure.
    • A pilot-navigation departure requires minimal controller intervention and organizes departing aircraft according to their initial routes.
      • Initial vectoring may be required.
      • Leave departure (heavy line) route at assigned transition points.
      • Departure transitions (lighter line) at the assigned route.
    • The DP may need to be discontinued to accommodate weather or traffic conditions.
    • Amendments may be issued as required.
    • Card is divided into a pictorial section and a text description.
    • Obstacle Departure Procedures:

      • ODPs provide obstruction clearance via the least onerous route from the terminal area to the appropriate enroute structure.
      • ODPs are recommended for obstruction clearance and may be flown without an ATC clearance unless an alternate departure procedure (SID/Radar Vectors) has been specifically assigned by ATC.
        • ODPs may be a great choice for VFR departures, especially at night, as obstacle clearance is never provided when not under positive control (Class G departures, etc).
        • If flown under VFR, advise ATC, if in controlled airspace, to remain predictable.
      • The FAA provides ODPs in both textual and graphical formats.
      • Graphic ODPs will have (OBSTACLE) printed in the procedure. []
      • DRAKE TWO (OBSTACLE) (RNAV)
        DRAKE TWO (OBSTACLE) (RNAV)
    • Standard Instrument Departures:

      • Instrument Flying Handbook, ODPs and SIDs
        Instrument Flying Handbook, ODPs and SIDs
      • Standard Instrument Departures are air traffic control (ATC) procedures printed for pilot/controller use in graphic form to provide obstruction clearance and a transition from the terminal area to the appropriate en route structure. []
      • Instrument Flying Handbook, ODPs and SIDs
        Instrument Flying Handbook, ODPs and SIDs
      • SIDs enhance system efficiency, reduce pilot and controller workload, and may also support noise-abatement procedures.
      • ATC clearance must be received prior to flying a SID.
    • RNAV Procedures:

      • RNAV procedures will have RNAV printed in the title. [/]
      • Public performance-based navigation (PBN) SIDs and graphic ODPs are normally designed using RNAV 1, required navigation performance (RNP) 1, or advanced required navigation performance (A-RNP) navigation specifications.
        • These procedures generally start with an initial track or heading leg near the departure end of runway (DER).
        • These procedures require navigation-system performance that may be provided by GPS (Global Positioning System) or compliant DME (distance measuring equipment)/DME/IRU (Inertial Reference Unit) RNAV systems meeting the applicable guidance in Advisory Circular (AC) 90-100A.
        • RNAV 1 and RNP 1 procedures must maintain a total system error of not more than 1 NM for 95% of the total flight time.
      • STAAV EIGHT DEPARTURE (RNAV)
        STAAV EIGHT DEPARTURE (RNAV)
  • Diverse Vector Area (DVA):

    • A Diverse Vector Area (DVA) is an area in which ATC may provide random radar vectors during an uninterrupted climb from the departure runway until above the MVA/MIA, established in accordance with the TERPS criteria for diverse departures.
    • The DVA provides obstacle and terrain avoidance instead of taking off from the runway under IFR using an ODP or SID.
  • Instrument Flying Handbook, ODPs and SIDs
    Instrument Flying Handbook, ODPs and SIDs
Departure Procedures

Obstacle Protection

  • Rate of Climb Table
    Rate of Climb Table
  • DPs are designed so that adherence to the procedure by the pilot will ensure obstacle protection.
    • Obstacle clearance responsibility rests with the pilot when he/she chooses to climb in visual conditions in lieu of flying a DP and/or depart under increased takeoff minima rather than fly the climb gradient.
    • Standard takeoff minima are one statute mile for aircraft having one or two engines and a half statute mile for aircraft having more than two engines.
    • Specified ceiling and visibility minima will allow visual avoidance of obstacles during the initial climb at the standard climb gradient.
    • When departing using the VCOA, obstacle avoidance is not guaranteed if the pilot maneuvers farther from the airport than the published visibility minimum for the VCOA before reaching the published VCOA altitude.
    • DPs may also contain what are called Low Close in Obstacles.
    • These obstacles require a higher than standard climb gradient within 1 NM of the departure end of runway, to an altitude of 200 feet or less above the departure end of runway elevation.
      • They do not require increased takeoff minimums.
    • These obstacles are identified on the graphic ODP or in the Take-off Minimums and (Obstacle) Departure Procedures section of the U. S. Terminal Procedure booklet. []
    • Takeoff minimums obstacles require a higher-than-standard climb gradient within 2.6 NM of the departure end of runway (DER), to an altitude greater than 200 feet above DER elevation, and increased takeoff minimums. Higher-than-standard ceiling and visibility minimums are published with the obstacle listing.
      • These obstacles are especially critical to aircraft that do not lift off until close to the departure end of the runway or that climb at the minimum rate.
      • Pilots should also consider drift following lift-off to ensure sufficient clearance from these obstacles.
    • When using higher than standard takeoff minimums, the portion requiring visual obstacle avoidance ends once the aircraft is beyond the published visibility distance or above the published ceiling height.
    • In all cases, continued obstacle clearance requires at least 200 feet per nautical mile to the specified point and thereafter until reaching the minimum en route altitude, unless a higher climb gradient is published. When a higher gradient is published and used, maintain it to its termination altitude, then continue at 200 feet per nautical mile until reaching the minimum en route altitude.
  • ATC may vector the aircraft beginning with an ATC-assigned heading issued with the initial or takeoff clearance, followed by subsequent vectors, if required, until reaching the minimum vectoring altitude by using a published Diverse Vector Area (DVA).
    • The DVA may be established below the Minimum Vectoring Altitude (MVA) or Minimum IFR Altitude (MIA) in a radar environment at the request of Air Traffic.
      • This type of DP meets the TERPS criteria for diverse departures, obstacles, and terrain avoidance in which radar vectors below the MVA/MIA may be issued to departing aircraft.
      • The DVA has been assessed for departures that do not follow a specific ground track but will remain within the specified area.
      • Use of a DVA is valid only when aircraft are permitted to climb uninterrupted from the departure runway to the MVA/MIA (or higher).
      • ATC will not assign an altitude below the MVA/MIA within a DVA.
      • At locations that have a DVA, ATC is not permitted to utilize a SID and DVA concurrently.
    • The existence of a DVA will be noted in the Takeoff Minimums and Obstacle Departure Procedure section of the U.S. Terminal Procedures Publication (TPP).
    • Boston Logan published Diverse Vector Area heading and runway climb requirements
      Boston DVA Example (October 1-29, 2026)
    • A DVA is identified by the heading "DIVERSE VECTOR AREA (RADAR VECTORS)." []
    • Boston Logan published Diverse Vector Area heading and runway climb requirements
      Boston DVA Example (October 1-29, 2026)
    • Pilots should be aware that Air Traffic facilities may utilize a climb gradient greater than the standard 200 FPNM in a DVA.
      • Pilots should note that the DVA has been assessed for departures which do not follow a specific ground track.
    • ATC may also vector an aircraft off a previously assigned DP.
      • If the aircraft is airborne and established on a SID or ODP and subsequently vectored off, ATC is responsible for terrain and obstruction clearance.
      • In all cases, the minimum 200 FPNM climb gradient is assumed.
      • As is always the case, when used by the controller during departure, the term "radar contact" should not be interpreted as relieving pilots of their responsibility to maintain appropriate terrain and obstruction clearance, which may include flying the obstacle DP.
    • Pilots must pre-plan to determine if the aircraft can meet the climb gradient (expressed in feet per nautical mile) required by the departure procedure, and be aware that flying at a higher than anticipated ground speed increases the climb rate requirement in feet per minute.
      • Higher than standard climb gradients are specified by a note on the departure procedure chart for graphic DPs, or in the Take-Off Minimums and (Obstacle) Departure Procedures section of the U.S. Terminal Procedures booklet for textual ODPs.
    • The required climb gradient, or higher, must be maintained to the specified altitude or fix, then the standard climb gradient of 200 ft/NM can be resumed.
    • A table for the conversion of climb gradient (feet per nautical mile) to climb rate (feet per minute), at a given ground speed, is included on the inside of the back cover of the U.S. Terminal Procedures booklets. []
    • Rate of Climb Table
      Rate of Climb Table
Departure Procedures

Departure Control

  • Departure Control is an approach control function responsible for ensuring separation between departures.
    • So as to expedite the handling of departures, Departure Control may suggest a takeoff direction other than that which may normally have been used under VFR handling.
    • Many times it is preferred to offer the pilot a runway that will require the fewest turns after takeoff to place the pilot on course or selected departure route as quickly as possible. At many locations particular attention is paid to the use of preferential runways for local noise abatement programs, and route departures away from congested areas.
  • When directed, contact departure control for handling out of the terminal area.
    • On initial contact after takeoff, report the altitude the aircraft is leaving and the assigned altitude. When cleared to "climb via" a departure, also report the SID name and any assigned restrictions not published on the procedure.
    • Controllers may omit the departure control frequency if a DP has or will be assigned and the departure control frequency is published on the DP.
  • Pilots will be advised to follow their clearance or maneuver for vectors:
    • Departure Control utilizing radar will normally clear aircraft out of the terminal area using vectors, a diverse vector area (DVA), or published DPs.
      • When a departure is to be vectored immediately following takeoff using vectors, a DVA, or published DPs that begins with an ATC assigned heading off the ground, the pilot will be advised prior to takeoff of the initial heading to be flown but may not be advised of the purpose of the heading.
      • When ATC assigns an initial heading with the takeoff clearance that will take the aircraft off an assigned procedure (for example, an RNAV SID with a published lateral path to a waypoint and crossing restrictions from the departure end of runway), the controller will assign an altitude to maintain with the initial heading and, if necessary, a speed to maintain.
    • At some airports when a departure will fly an RNAV SID that begins at the runway, ATC may advise aircraft of the initial fix/waypoint on the RNAV route.
      • The purpose of the advisory is to remind pilots to verify the correct procedure is programmed in the FMS (Flight Management System) before takeoff.
      • Pilots must immediately advise ATC if a different RNAV SID is entered in the aircraft's FMS.
      • When this advisory is absent, pilots are still required to fly the assigned SID as published.
        • ATC: "Delta 345 RNAV to MPASS, Runway 26L, cleared for takeoff."
        • The SID transition is not restated as it is contained in the ATC clearance.
        • Aircraft cleared via RNAV SIDs designed to begin with a vector to the initial waypoint are assigned a heading before departure.
    • Pilots operating in a radar environment are expected to associate departure headings or an RNAV departure advisory with vectors or the flight path to their planned route or flight.
      • When given a vector taking the aircraft off a previously assigned non-radar route, the pilot will be advised briefly what the vector is to achieve.
      • Thereafter, radar service will be provided until the aircraft has been reestablished "on-course" using an appropriate navigation aid and the pilot has been advised of the aircraft's position or a handoff is made to another radar controller with further surveillance capabilities.
  • Controllers will inform pilots of the departure control frequencies and, if appropriate, the transponder code before takeoff.
    • Pilots must ensure their transponder/ADS-B is adjusted to the "on" or normal operating position as soon as practical and remain on during all operations unless otherwise requested to change to "standby" by ATC.
    • Pilots should not change to the departure control frequency until requested.
    • Controllers may omit the departure control frequency if a DP has or will be assigned and the departure control frequency is published on the DP.
Departure Procedures

Departure Clearances

  • Departure clearances are typically assigned with your initial contact with clearance delivery (or via pre-taxi clearance).
  • If you accept a SID as part of your clearance, comply with all specified routings, altitudes, and specific restrictions.
    • SIDs must be followed regardless of weather conditions, unless a deviation is approved by ATC.
  • Consider SID canceled if aircraft is vectored or cleared off SID-specified course, unless ATC adds "expect to resume SID" or otherwise indicates the deviation is temporary.
  • When ATC reinstates a canceled SID, it must specify the routing to resume.
    • Applicable altitude and speed restrictions must be reissued, or reinstated with "climb via SID" or "resume published speed," as appropriate.
  • A "climb and maintain" clearance cancels previously published SID altitude restrictions unless ATC restates them.
    • The SID path-over-the-ground must still be followed even though a climb to higher altitude has commenced.
    • A "climb via SID except maintain" clearance changes the cleared top altitude while retaining the other applicable SID restrictions.
  • Pre-taxi Clearance Procedures:

    • Pre-Taxi Clearance Note
      Pre-Taxi Clearance Note
    • Certain airports have established pre-taxi clearance programs whereby pilots of departing instrument flight rules (IFR) aircraft may elect to receive their IFR clearances before they start taxiing for takeoff.
    • Locations where these procedures are in effect are indicated in the Chart Supplement U.S. []
    • The following provisions apply:
      • Pilot participation is not mandatory.
      • Participating pilots call clearance delivery or ground control not more than 10 minutes before proposed taxi time.
      • IFR clearance (or delay information, if clearance cannot be obtained) is issued at the time of this initial call-up.
      • When the IFR clearance is received on clearance delivery frequency, pilots call ground control when ready to taxi.
      • Normally, pilots need not inform ground control that they have received IFR clearance on clearance delivery frequency.
        • Certain locations may, however, require that the pilot inform ground control of a portion of the routing or that the IFR clearance has been received.
      • If a pilot cannot establish contact on clearance delivery frequency or has not received an IFR clearance before ready to taxi, the pilot should contact ground control and inform the controller accordingly.
    • Pre-Taxi Clearance Note
      Pre-Taxi Clearance Note
  • Abbreviated IFR Departure Clearance Procedures:

    • ATC facilities will issue an abbreviated IFR departure clearance based on the ROUTE of flight filed in the IFR flight plan, provided the filed route can be approved with little or no revision.
    • These abbreviated clearance procedures are based on the following conditions:
      • The aircraft is on the ground or it has departed visual flight rules (VFR) and the pilot is requesting IFR clearance while airborne.
      • That a pilot will not accept an abbreviated clearance if the route or destination of a flight plan filed with ATC has been changed by the pilot or the company or the operations officer before departure.
      • That it is the responsibility of the company or operations office to inform the pilot when they make a change to the filed flight plan.
      • That it is the responsibility of the pilot to inform ATC in the initial call-up (for clearance) when the filed flight plan has been either:
        • Amended, or
        • Canceled and replaced with a new filed flight plan.
      • Note the facility issuing a clearance may not have received the revised route or the revised flight plan by the time a pilot requests clearance.
    • Controllers will issue a detailed clearance when they know that the original filed flight plan has been changed or when the pilot requests a full route clearance.
    • The clearance as issued will include the destination airport filed in the flight plan, any DPs flown, and then cleared as filed.
    • When no changes are required in the filed route, state the phrase: "Cleared to (destination) airport, (SID and SID transition, as appropriate); then, as filed." If a SID is not assigned, follow with "As filed."
    • For all departure clearances when a Departure Procedure (DP) or DP transition is to be flown, the controller must state the DP name, current DP number, and DP transition name after “Cleared to [destination] airport” and before “then as filed,” whether or not the DP was filed.
    • STARs (Standard Terminal Arrivals), when filed in a flight plan, are considered a part of the filed route of flight and will not normally be stated in an initial departure clearance.
      • If the ARTCC (Air Route Traffic Control Center)'s jurisdictional airspace includes both the departure airport and the fix where a STAR or STAR transition begins, the STAR name, the current number and the STAR transition name MAY be stated in the initial clearance.
    • "Cleared to (destination) airport as filed" does NOT include the en route altitude filed in a flight plan.
      • An en route altitude will be stated in the clearance or the pilot will be advised to expect an assigned or filed altitude within a given time frame or at a certain point after departure.
      • This may be done verbally in the departure instructions or stated in the DP.
    • In both radar and non-radar environments, the controller will state "Cleared to (destination) airport as filed" or:
      • If a DP or DP transition is to be flown, specify the DP name, the current DP number, the DP transition name, the assigned altitude/flight level, and any additional instructions (departure control frequency, beacon code assignment, etc.) necessary to clear a departing aircraft via the DP or DP transition and the route filed.
        • "National Seven Twenty cleared to Miami Airport Intercontinental one departure, Lake Charles transition then as filed, maintain Flight Level two seven zero."
      • When there is no DP or when the pilot cannot accept a DP, the controller will specify the assigned altitude or flight level, and any additional instructions necessary to clear a departing aircraft via an appropriate departure routing and the route filed.
        • Note that a detailed departure route description or a radar vector may be used to achieve the desired departure routing.
      • If it is necessary to make a minor revision to the filed route, the controller will specify the assigned DP or DP transition (or departure routing), the revision to the filed route, the assigned altitude or flight level and any additional instructions necessary to clear a departing aircraft.
        • "Jet Star One Four Two Four cleared to Atlanta Airport, South Boston two departure then as filed except change route to read South Boston Victor 20 Greensboro, maintain one seven thousand."
      • Additionally, in a non-radar environment, the controller will specify one or more fixes, as necessary, to identify the initial route of flight.
        • "Cessna Three One Six Zero Foxtrot cleared to Charlotte Airport as filed via Brooke, maintain seven thousand."
    • To ensure success of the program, pilots should:
      • Avoid making changes to a filed flight plan just prior to departure.
      • State the following information in the initial call-up to the facility when no change has been made to the filed flight plan: Aircraft call sign, location, type operation (IFR) and the name of the airport (or fix) to which you expect clearance.
        • "Washington clearance delivery (or ground control if appropriate) American Seventy Six at gate one, IFR Los Angeles."
    • If the flight plan has been changed, state the change and request a full route clearance.
      • "Washington clearance delivery, American Seventy Six at gate one. IFR San Francisco. My flight plan route has been amended (or destination changed). Request full route clearance."
    • Request verification or clarification from ATC if ANY portion of the clearance is not clearly understood.
    • When requesting clearance for the IFR portion of a VFR/IFR flight, request such clearance prior to the fix where IFR operation is proposed to commence in sufficient time to avoid delay. Use the following phraseology:
      • "Los Angeles center, Apache Six One Papa, VFR estimating Paso Robles VOR at three two, one thousand five hundred, request IFR to Bakersfield."
  • Automated Pre-Departure Clearance Procedures:

    • Many airports in the National Airspace System are equipped with the Terminal Data Link System (TDLS) that includes the Pre-Departure Clearance (PDC) and Controller Pilot Data Link Communication–Departure Clearance (CPDLC-DCL) functions.
      • Both the PDC and CPDLC-DCL functions automate the Clearance Delivery operations in the ATCT (Airport Traffic Control Tower) for participating users.
      • Both functions display IFR clearances from the ARTCC to the ATCT.
    • The Clearance Delivery controller in the ATCT can append local departure information and transmit the clearance via data link to participating airline/service provider computers for PDC.
      • The airline/service provider will then deliver the clearance via the Aircraft Communications Addressing and Reporting System (ACARS) or a similar data link system, or for non-data link equipped aircraft, via a printer located at the departure gate.
    • For CPDLC-DCL, the departure clearance is uplinked from the ATCT via the Future Air Navigation System (FANS) to the aircraft avionics and requires a response from the flight crew.
    • Both PDC and CPDLC-DCL reduce frequency congestion, controller workload, and are intended to mitigate delivery/read back errors.
      • Both services are available only to participating aircraft that have subscribed to the service through an approved service provider.
    • In all situations, the pilot is encouraged to contact clearance delivery if a question or concern exists regarding an automated clearance.
    • FAA Mobile Clearance allows participating Part 91 and Part 135 pilots at supported airports to request IFR departure clearances through ForeFlight or Garmin and, where available, cancel IFR through the application after landing at a nontowered airport.
      • After filing through a supported application, request the clearance when the option becomes available; ATC can then transmit the complete clearance, amendments, and remarks to the electronic flight bag.
      • Review the complete clearance—including the clearance limit, route, altitude, departure frequency, transponder code, and remarks—before accepting or using it.
      • If any part of the clearance is unclear or requires a change, reject it and contact ATC through the normal radio or telephone method.
      • When Mobile Clearance becomes available at a nontowered airport, a clearance containing a hold-for-release instruction does not authorize departure; obtain a verbal release from ATC, and do not depart VFR using the assigned IFR transponder code as a substitute for that release.
    • Mobile Clearance remains under operational evaluation at selected locations, with deployment to additional airports across the United States scheduled to begin in 2027; pilots must verify current airport and application availability before relying on the service.
    • On initial ground-control contact, advise the controller that the clearance was received through Mobile Clearance.
    • Limitations/differences exist between the two services:
      • Pre-Departure Clearance:
        • Aircraft filing multiple flight plans are limited to one PDC clearance per departure airport within an 18-hour period. Additional clearances will be delivered verbally.
        • If the clearance is revised or modified prior to delivery, it will be rejected from PDC and the clearance will need to be delivered verbally.
        • No acknowledgment of receipt or read back is required for a PDC.
      • Controller Pilot Data Link Communication–Departure Clearance:
        • No limitation to the number of clearances received.
        • Allows delivery of revised flight data, including revised departure clearances.
        • A response from the flight crew is required.
        • Requires a logon to the FAA National Single Data Authority - KUSA - utilizing the ATC FANS application.
        • To be eligible, operators must have received CPDLC (Controller-Pilot Data Link Communications)/FANS authorization from the responsible civil aviation authority, and file appropriate equipment information in ICAO (International Civil Aviation Organization) field 10a and in the ICAO field 18 DAT (Other Data Applications) of the flight plan.
Departure Procedures

Departure Restrictions

  • ATC may assign departure restrictions, clearance void times, hold for release, and release times as needed to separate departures from other traffic or manage departure flow.
  • Before an IFR departure from an airport without an operating control tower, ATC must issue either a departure release, with a release time and/or void time when applicable, or a hold for release.
  • Clearance Void Times:

    • When departing from an airport without a control tower, a pilot may receive a clearance void time requiring the aircraft to be airborne before the specified time.
    • If unable to depart before the clearance void time, the pilot must advise ATC as soon as possible of their intentions.
    • ATC normally specifies a notification deadline for reporting that the aircraft did not depart before the clearance void time.
    • The allotted notification period cannot exceed 30 minutes after the clearance void time.
    • If the aircraft has not contacted ATC within 30 minutes after the clearance void time, it is considered overdue and search and rescue procedures are initiated.
      • Other IFR traffic at the airport is suspended until the aircraft contacts ATC or until 30 minutes after the clearance void time; if no void time was issued, the interval is measured from the clearance release time.
      • Expiration of the clearance void time does not cancel the departure clearance or IFR flight plan.
        • It withdraws authority to depart IFR until ATC issues a new departure release or release time and the pilot acknowledges it.
      • Departing IFR at or after the clearance void time without a new release provides no IFR separation and may violate 14 CFR Section 91.173, which requires an appropriate ATC clearance for IFR flight in controlled airspace.
      • Pilots who depart VFR after the clearance void time expires should not use the previously assigned IFR transponder code.
      • ATC: "Clearance void if not off by [clearance void time] and, if required, if not off by [clearance void time] advise [facility] not later than [time] of intentions".
      • Do not confuse this notification period with the recommendation to file an IFR flight plan at least 30 minutes before departure.
  • Hold for Release:

    • Air traffic control (ATC) may issue "hold for release" to delay departure for traffic management reasons, such as weather or traffic volume.
    • The pilot may not depart under that instrument flight rules (IFR) clearance until ATC issues a release time or additional instructions.
    • ATC will include expected departure-delay information with the hold-for-release instruction.
    • Hold for release applies only to the IFR clearance and does not prohibit departure under visual flight rules (VFR).
      • If conditions permit, the pilot may cancel the IFR flight plan and depart under VFR.
        • Before departing VFR, operate the transponder/ADS-B on the appropriate VFR code.
      • The reason for the delay may remain, so an IFR clearance might not be available after departure.
        • ATC: "[Aircraft identification] cleared to [destination] airport as filed, maintain [altitude], and, if required [additional instructions or information], hold for release, expect [time in hours and/or minutes] departure delay."
  • Release Times:

    • A release time is an ATC departure restriction specifying the earliest time an aircraft may depart.
    • ATC uses release times for traffic management and/or to separate departing aircraft from other traffic.
      • ATC: "[Aircraft identification] released for departure at [time in hours and/or minutes]."
  • Expect Departure Clearance Time:

    • The Expect Departure Clearance Time (EDCT) is the runway release time assigned to an aircraft subject to a traffic management program.
      • The aircraft is expected to depart no earlier than 5 minutes before and no later than 5 minutes after its EDCT.
    • Pilots may hear clearance delivery/ground control state: "[Callsign] you have an EDCT time of 1356, acknowledge."
    • Receiving an IFR clearance early does not authorize departure outside the EDCT window.
    • When practical and two-way communication with the controlling ATC facility is available, pilots departing airports without an operating control tower should obtain their IFR clearance before becoming airborne.
    • Because an EDCT can change, the FAA recommends pilots confirm their flight's EDCT 45 minutes or less before departure.
Departure Procedures

Additional Restrictions/Limitations

  • Unless otherwise specified, departure procedures assume the pilot will cross the departure end of the runway at least 35' above the runway and climbing to 400' above the departure end elevation before making initial turn and then maintaining a standard 200' per NM conforming to the departure altitude limits.
    • It is important that you are aware if your aircraft can perform to the restrictions on the DP.
    • To calculate climb rate required (feet per minute) to meet or exceed the climb gradient (feet per nautical mile) you can either calculate it manually or use the chart on the back of the terminal approach plate publication.
    • Take your ground speed in nautical miles per hour, divide by 60 minutes per hour, and multiply by the climb gradient in feet per nautical mile.
  • Departure procedures may be amended by a Notice to Airmen (NOTAM). Pilots must review all applicable NOTAMs during preflight planning.
  • DPs primarily provide obstacle-clearance protection when flown as published; at busier airports, SIDs may also increase efficiency and reduce communications and departure delays.
  • During departure, pilots remain responsible for obstacle clearance unless ATC assumes that responsibility by providing radar vectors.
    • Being told "radar contact" alone does not transfer this responsibility to ATC.
  • If the pilot does not possess a DP or does not wish to use one (due to gradient, equipment required, or other reason), he/she is expected to advise ATC.
    • For SIDs, this may be accomplished by stating "NO SID" in the remarks section of the flight plan or by verbally advising ATC, but will likely result in a delay or deviation for departure.
    • Pilots operating under Part 91, whether IFR rated or not, are strongly encouraged to use the ODP system and SIDs in marginal VFR conditions and at night when operating VFR.
  • At locations with airport traffic control service, when necessary, ATC specifies the takeoff direction, turn, or initial heading to be flown after takeoff, consistent with published departure procedures (DP) or diverse vector areas (DVA), where applicable.
  • At locations without airport traffic control service but within a Class E surface area, ATC obtains pilot concurrence when specifying the takeoff direction, turn, or initial heading, to confirm that the pilot can comply with local traffic patterns and terrain and obstruction avoidance.
Departure Procedures

Departure Procedures Responsibilities

  • Takeoff Minimums
    Takeoff Minimums
  • Bennington, VT Textual Departure Procedure
    Bennington, VT Textual Departure Procedure
  • Pilot Responsibilities:

    • Assess terrain and obstacles on and near the departure airport.
    • Determine whether an obstacle departure procedure (ODP) or another departure procedure (DP) is available.
      • A published Visual Climb Over Airport (VCOA) may be another option.
        • Advise ATC as early as possible before departure if intending to fly the VCOA.
    • Determine whether obstacles can be avoided visually or the ODP should be flown.
      • At airports without published instrument approach procedures (IAPs) and therefore without a published departure procedure, determine and take the actions necessary for a safe departure.
    • Consider degraded climb performance and plan the actions to take following an engine failure during departure.
      • Notify ATC as soon as possible if an engine failure reduces climb capability.
    • Determine whether a diverse vector area (DVA) is published and whether the aircraft can meet its published climb gradient.
      • If unable to meet the gradient, advise ATC when requesting the IFR clearance, or as soon as possible.
    • Check for Takeoff Obstacle Notes published in the Terminal Procedures Publication (TPP) for the takeoff runway. [/]
    • Do not exceed a published SID waypoint speed restriction until passing that waypoint.
    • If vectored or cleared to deviate off a SID or SID transition after becoming established, consider the SID canceled unless ATC states "expect to resume SID."
      • If told "expect to resume SID," be prepared to rejoin at a subsequent fix or procedure leg.
      • When vectored or cleared off the SID, its published altitude and speed restrictions are canceled; ATC will assign an altitude to maintain and, if necessary, a speed.
      • ATC may also interrupt vertical navigation and assign alternate altitude instructions while the aircraft remains on the published lateral path.
      • An ODP is canceled if ATC vectors the aircraft off it or assigns an altitude lower than a published ODP altitude.
      • In these cases, ATC assumes responsibility for terrain and obstacle clearance.
      • A minimum climb gradient of 200 feet per nautical mile (FPNM) is still assumed.
    • When instructing an aircraft to resume a SID with altitude and/or speed restrictions, ATC must:
      • Issue or reissue all applicable restrictions; or
      • Instruct the pilot to "climb via SID" or "resume published speed", as applicable.
      • EXAMPLE: "Resume the Solar One departure, climb via SID."
      • EXAMPLE: "Proceed direct CIROS, resume the Solar One departure, climb via SID."
    • For a SID without published crossing restrictions, a SID with a radar-vector segment, or a radar-vector SID, ATC uses "Maintain [altitude]" to assign the altitude.
    • A "climb via" clearance for a SID with published altitude restrictions requires compliance with the lateral path, speed restrictions, and altitude restrictions along the cleared route and authorizes the pilot to:
      • Join the procedure after departure or resume it when the climb-via clearance is issued in the IFR departure clearance, a pre-departure clearance (PDC), a data link clearance (DCL), or a clearance to a waypoint depicted on the SID.
      • After vertical navigation has been interrupted by an assigned altitude not published on the procedure, climb at pilot's discretion from that altitude to the altitude depicted for the next waypoint when cleared to climb via.
      • Once established on the departure, follow the lateral path and climb to meet all published or assigned altitude and speed restrictions.
      • See also: Bold Method - How To Fly An IFR Departure Procedure With 'Climb Via.'
    • Comply with published speed restrictions along the cleared route or procedure even without a climb-via clearance.
    • Begin adjusting speed only as far in advance as necessary to cross the waypoint or fix at the published speed.
      • Maintain that speed until another published or ATC-assigned restriction requires adjustment, or until adjustment is needed to comply with 14 CFR Section 91.117.
    • If ATC interrupts lateral or vertical navigation on a SID, ATC must ensure obstacle clearance.
      • When issuing a climb-via clearance to join or resume the SID, ATC retains this responsibility until the aircraft is established on the SID's lateral and vertical path.
    • When clearing an aircraft direct to a waypoint or fix to join or resume a SID, ATC assigns a crossing altitude if none is published or if otherwise necessary.
    • A SID's top altitude is the charted "maintain" altitude in the procedure description or an altitude assigned by ATC.
    • On initial contact with ATC after a climb-via clearance, report the altitude leaving and any assigned restrictions not published on the procedure.
      • (Cactus 711 is cleared to climb via the Laura Two departure. The Laura Two has a top altitude of FL190): "Cactus Seven Eleven leaving two thousand, climbing via the Laura Two departure."
      • (Cactus 711 is cleared to climb via the Laura Two departure, but ATC changed the top altitude to 16,000): "Cactus Seven Eleven leaving two thousand for one-six thousand, climbing via the Laura Two departure."
    • A "climb and maintain" clearance cancels previously issued SID altitude restrictions unless ATC restates them.
      • Published speed restrictions and lateral-path requirements remain in effect unless ATC cancels them.
      • A "climb via SID except maintain" clearance changes the top altitude while retaining the other published restrictions.
      • For example, ATC may replace a climb-via clearance with a climb-and-maintain clearance before or after takeoff:
        • "Climb and maintain flight level two four zero."
        • The SID altitude restrictions are canceled; follow the SID lateral path and climb unrestricted to FL240.
          • Published speed restrictions still apply unless ATC specifically cancels them.
    • ODP altitude restrictions provide obstacle clearance and/or satisfy procedure-design constraints.
      • ATC cannot cancel or amend crossing altitudes or speed restrictions on an ODP.
  • Controller Responsibilities:

    • At locations with airport traffic control service, ATC specifies the takeoff direction, turn, or initial heading when necessary, consistent with published departure procedures (DP) or diverse vector areas (DVA), where applicable.
    • At locations without airport traffic control service but within a Class E surface area, ATC obtains pilot concurrence before specifying a necessary takeoff direction, turn, or initial heading, confirming that the pilot can comply with local traffic patterns and avoid terrain and obstructions.
    • When an initial heading takes the aircraft off an assigned procedure, ATC assigns an altitude to maintain with the initial heading (for example, when departing an RNAV SID with a published lateral path to a waypoint and crossing restrictions from the departure end of the runway).
    • ATC includes established departure procedures in the clearance when pilot compliance is necessary to ensure separation.
    • At locations with both SIDs and DVAs, ATC issues an amended departure clearance to cancel the previously assigned SID before using a DVA, or vice versa.
      • ATC provides the amended clearance early enough for the pilot to confirm adequate climb performance, determine whether the clearance is acceptable, and brief the changes before entering the runway.
    • At locations with a DVA, ATC must not use a SID and DVA concurrently.
  • Takeoff Minimums
    Takeoff Minimums
  • Bennington, VT Textual Departure Procedure
    Bennington, VT Textual Departure Procedure
Departure Procedures

Locating Departure Procedures

  • Minimum Safe Altitude
    Minimum Safe Altitude
  • Minimum Safe Altitude:

    • The FAA publishes Minimum Safe/Sector Altitudes (MSAs) on IAP charts and departure procedure (DP) graphic charts for emergency use.
    • MSAs provide 1,000 feet of clearance over all obstacles but do not necessarily ensure acceptable navigation signal coverage, as with Off-Route Obstruction Clearance Altitudes (OROCAs).
    • The MSA depiction in an approach chart’s plan view or on a DP graphic chart includes: []
      • The identifier of the MSA center point (NAVAID/RNAV waypoint).
      • The MSA radius is normally 25 NM. For conventional navigation systems, it may be expanded to 30 NM if necessary to encompass the airport landing surfaces.
      • Up to four sectors, with minimum altitudes above mean sea level that provide obstacle clearance.
    • For conventional navigation systems, the MSA is normally centered on the primary omnidirectional facility used by the procedure, but may be centered on the airport reference point (ARP) if no suitable facility is available.
    • For RNAV approaches and graphical departure procedures, the MSA is centered on an RNAV waypoint.
    • Minimum Safe Altitude
      Minimum Safe Altitude
  • Complex Obstacle Departure
    Complex Obstacle Departure
  • Obstacle Departure
    Obstacle Departure
  • T Symbol
    T Symbol
  • Graphic ODP Reference
    Graphic ODP Reference
  • Textual departure procedures and diverse vector areas are listed by airport in Section L, “IFR Takeoff Minimums and (Obstacle) Departure Procedures,” of the Terminal Procedures Publication (TPP). SIDs and complex ODPs are published graphically and named; their names are listed by airport and runway in Section L.
  • They can be found on websites like airnav.com or in print from vendors such as AeroNav. []
  • Terminal Procedures Publication Booklet:

    • The purpose of noting obstacles in the "Take-off Minimums and (OBSTACLE) Departure Procedures" section of the TPP is to identify the obstacle(s) and alert the pilot to the height and location of the obstacle(s) so they can be avoided.
      • This can be accomplished in a variety of ways; for example, the pilot may be able to see the obstruction and maneuver around the obstacle(s) if necessary; early liftoff/climb performance may allow the aircraft to cross well above the obstacle(s); or if the obstacle(s) cannot be visually acquired during departure, delay takeoff or select another runway for the IFR departure.
      • The TPP may contain either legacy or revised takeoff-obstacle note formats while departure procedures are being updated.
        • Legacy notes combine low, close-in and takeoff-minimums obstacles for each runway; revised notes separate these categories and include a DER crossing height that clears obstacles penetrating the 40:1 obstacle clearance surface (OCS).
        • Bolded headings and runway information identify which evaluation was used.
      • EXAMPLE: LEGACY TAKEOFF OBSTACLE NOTES: Rwy 14, trees 2011' from DER, 29' left of centerline, 100' AGL (Above Ground Level)/3829' MSL (Mean Sea Level). Rwy 32, trees 1009' from DER, 697' left of centerline, 100' AGL/3839' MSL. Tower 4448' from DER, 1036' left of centerline, 165' AGL/3886' MSL.
    • Graphic ODPs will also have the term "(OBSTACLE)" printed in the charted procedure title, differentiating them from SIDs. []
  • Instrument Approach Charts:

    • An ODP that has been developed solely for obstacle avoidance will be indicated with the symbol "T" on appropriate Instrument Approach Procedure (IAP) charts and DP charts for that airport. []
    • The "T" symbol will continue to refer users to Section L of the TPP.
    • In the case of a graphic ODP, the TPP Section L will only contain the name of the ODP.
    • Complex Obstacle Departure
      Complex Obstacle Departure
    • Obstacle Departure
      Obstacle Departure
    • T Symbol
      T Symbol
    • Graphic ODP Reference
      Graphic ODP Reference
    • Since there may be both a textual and a graphic DP, Section L should still be checked for additional information.
    • The nonstandard takeoff minimums and minimum climb gradients found in TPP Section L also apply to charted DPs and radar vector departures unless different minimums are specified on the charted DP. []
    • Takeoff minimums and departure procedures apply to all runways unless otherwise specified.
    • New graphic DPs will have all the information printed on them.
    • As a general rule, ATC will only assign an ODP from a non-towered airport when compliance with the ODP is necessary for aircraft-to-aircraft separation.
    • Pilots may use the ODP to help ensure separation from terrain and obstacles.
Departure Procedures

Departure Procedure

  1. Review current weather, applicable NOTAMs, published takeoff minimums, obstacle notes, and available departure procedures.
    • The standard visibility minimums in Title 14 of the Code of Federal Regulations (CFR) 91.175(f) apply to the operations identified in that paragraph, but not to an operation conducted solely under Part 91.
    • Confirm that the aircraft can satisfy the required climb gradient, equipment requirements, and any published altitude or speed restrictions.
  2. File the IFR flight plan.
  3. Obtain the departure clearance with clearance delivery.
    • UHF: "[place] clearance delivery, [call sign], IFR to [destination], clearance on request."
    • UHF: "[Callsign] I have your clearance, advise when ready to copy."
  4. Read back and verify the cleared route, initial altitude, assigned transponder code, departure frequency, and any hold-for-release, release-time, or clearance-void-time restriction.
    • UHF: "[place] clearance, [call sign], ready to copy."
  5. Program the cleared route and departure procedure into the navigation system.
    • Independently verify all fixes, courses, restrictions, and transitions against the current published procedure.
  6. TUNE & ID: Identify the required NAVAIDs (Navigational Aids) for the departure if possible.
  7. TOGGLE & TWIST: the appropriate course and check for VOR (Very High Frequency Omnidirectional Range)/TACAN (Tactical Air Navigation) switch in the appropriate position for departure.
  8. At a towered airport, obtain the appropriate taxi and takeoff clearances. At a nontowered airport, comply with the applicable release, hold-for-release, or clearance-void-time instructions.
    • UHF: "[place] ground, [call sign] at [parking spot] taxi with [ATIS information]."
  9. Contact the tower for takeoff and comply with any special instructions provided.
    • UHF: "[place] tower, [call sign], [place] takeoff."
  10. Brief the runway, initial flight path, required climb gradient, altitude and speed restrictions, anticipated frequencies, and applicable contingency actions.
  11. After takeoff, fly the cleared lateral path and comply continuously with all published and assigned altitude, speed, and climb-gradient restrictions.
  12. When directed, switch to departure control and make the off report.
    • On initial contact, report the aircraft’s identification, current altitude, and assigned altitude.
      • For a climb-via clearance, also report the SID name and any assigned restrictions not published on the procedure.
    • UHF: "[place] departure, [call sign], off [place], passing [altitude] for [altitude]."
  13. Comply with radar vector departure or DP instructions as appropriate until it terminates or ATC issues an amended clearance.
  14. At the completion of the procedure, accelerate to cruise speed, unless something is restricting you from doing so.
    • The departure phase is complete after flying the DP and joining the en route structure.
      • "Resume own navigation" returns navigational responsibility to the pilot; it does not necessarily mean the departure is complete.
    • An instruction to “resume own navigation” does not by itself cancel restrictions that remain applicable.
Departure Procedures

Visual Climb Over Airport (VCOA)

  • Visual Climb Over Airport (VCOA)
  • FAA Broken Bow Runway 32 VCOA: 1100-3; obtain ATC approval when requesting IFR clearance, then climb visually to cross the airport at or above 3500 feet before proceeding on course.
    FAA Broken Bow (KBBW), Published VCOA Excerpt
  • A Visual Climb Over Airport (VCOA) procedure allows an IFR aircraft an option to depart in visual meteorological conditions by conducting climbing turns over the airport to the published “at or above” altitude.
    • VCOAs can provide an alternative when an aircraft cannot meet a departure’s required climb gradient and a Diverse Vector Area (DVA) is unavailable.
  • After reaching this altitude, the pilot may enter instrument meteorological conditions and use a diverse departure to the first en route fix or follow published routing to join the IFR en route structure, maintaining a climb gradient of at least 200 feet per nautical mile.
  • The FAA develops VCOA procedures to avoid obstacles more than three statute miles from the departure end of the runway, providing an alternative to climb gradients greater than 200 feet per nautical mile.
  • Pilots must advise ATC as early as possible before departure of their intent to fly the VCOA option.
  • During the visual climb, pilots must remain within the distance prescribed by the published visibility minimums until reaching the VCOA "at or above" altitude.
  • If no additional routing is published, proceed in accordance with the IFR clearance after reaching the VCOA "at or above" altitude.
  • If additional routing is published beyond the "at or above" altitude, pilots must follow the published route, which may include a climb in holding to reach the minimum en route altitude (MEA) or minimum IFR altitude (MIA).
  • VCOA procedures are published in the Takeoff Minimums and (Obstacle) Departure Procedures section of the Terminal Procedures Publication (TPP) and/or as an option on a graphic obstacle departure procedure (ODP). []
    • Example: TAKE-OFF MINIMUMS: Rwy 32, standard with minimum climb of 410' per NM to 3000' or 1100-3 for VCOA. VCOA: Rwy 32, when executing VCOA, notify ATC prior to departure. Climb in visual conditions to cross Broken Bow Muni/Keith Glaze Field at or above 3500' before proceeding on course.
      • The published Broken Bow excerpt shows a 310-foot-per-NM climb alternative and requires ATC approval for VCOA when requesting IFR clearance; the AIM example above uses 410 feet per NM and different ATC wording.
  • Visual Climb Over Airport (VCOA)
  • FAA Broken Bow Runway 32 VCOA: 1100-3; obtain ATC approval when requesting IFR clearance, then climb visually to cross the airport at or above 3500 feet before proceeding on course.
    FAA Broken Bow (KBBW), Published VCOA Excerpt
Departure Procedures

PBN Departure Procedures

  • Public PBN (Performance-Based Navigation) SIDs and graphic ODPs are normally designed using RNAV 1, RNP (Required Navigation Performance) 1, or A-RNP (Advanced Required Navigation Performance) NavSpecs. These procedures generally start with an initial track or heading leg near the departure end of the runway (DER). In addition, these procedures require system performance currently met by GPS or DME/DME/IRU PBN systems that satisfy the criteria discussed in the latest AC 90-100, U.S. Terminal and En Route Area Navigation (RNAV) Operations. RNAV 1 and RNP 1 procedures must maintain a total system error of not more than 1 NM for 95 percent of the total flight time. Minimum values for A-RNP procedures will be charted in the PBN box (for example, 1.00 or 0.30).
  • In the U.S., charts prominently display a procedure's specific PBN requirements in separate, standardized note boxes. For procedures with PBN elements, the "PBN box" will contain the procedure's NavSpec(s) and, if required, specific sensors or infrastructure needed for the navigation solution, any additional or advanced functional requirements, the minimum RNP value, and any amplifying remarks. Items listed in this PBN box are REQUIRED for the procedure's PBN elements.
Departure Procedures

Departure Procedure Exercises

Departure Procedures

Departure Procedures Knowledge Check

Choose the knowledge check that matches your current training for Departure Procedures.

Private Pilot quiz illustration Private Pilot

PPL knowledge check

Core Knowledge Review

Review foundational knowledge, key concepts, and practical considerations. Topic: Departure Procedures.

  • Immediate feedback
  • Answer explanations
  • Account progress tracking

Why Take a Quiz?

Quizzes reinforce key concepts, identify knowledge gaps, and build confidence for real-world decisions. Quiz material is representative of the information provided here and is not based on or sourced from the Federal Aviation Administration test bank.

Departure Procedures

Departure Procedures Interactive Scenario

Fly the ZEFFR NINE: Clearance to DARBI

Work through a real Reno RNAV departure from the draft clearance through the DARBI transition using one complete FAA chart. Climb-gradient calculations, restrictions, automation checks, and “what if” branches advance with your decisions.

20 Decisions Real FAA Procedure Retry and Debrief
Example textual obstacle departure procedure used for departure planning.

The Ridge Valley IFR Departure

Plan and fly a terrain-constrained IFR departure through Climb-gradient, obstacle, route, automation, and radar-vector decisions from the runway to the enroute structure.

15 DecisionsScenario-Based TrainingDeparture ProceduresConsequence-BasedRetry and Debrief
Decision 1
0%

Scenario Complete

Departure Procedures

Departure Procedures Conclusion

  • Beyond Proficient: IFR Series | How to Depart Safely in Low IMC
  • ATC may assign DPs, and likewise, pilots can request them.
  • For operations conducted solely under Part 91, an ODP is not mandatory unless included in the ATC clearance.
    • During departure, pilots remain responsible for obstacle clearance unless ATC assumes that responsibility by providing radar vectors.
      • Being told "radar contact" alone does not transfer this responsibility to ATC.
  • As part of preflight planning, evaluate published takeoff minimums, obstacle departure procedures, required climb gradients, aircraft performance, and all limitations applicable to the operation.
  • Pilots operating under 14 CFR Part 91 are strongly encouraged to file and fly a DP at night, during marginal Visual Meteorological Conditions (VMC) and Instrument Meteorological Conditions (IMC), when one is available.
  • Air Traffic Control may substitute published departure procedures for radar vectors when able.
  • A period (.) after a sentence means you will not proceed any further until you have accomplished that instruction.
  • More detailed information on obstacle assessments is available in Advisory Circular AC 120-91, Airport Obstacle Analysis, and in the "Departure Procedures" section of chapter 1 in the Instrument Procedures Handbook.
  • Pilots can practice listening to, copying down, and understanding departure instructions through the use of LiveATC and FlightAware.
  • Establishing a thorough scan ensures pilots can maintain flight parameters as the aircraft transitions into and out of IMC, especially at night.
  • The standard takeoff visibility minimums in 14 CFR 91.175(f) are not regulatory for an operation conducted solely under Part 91. This does not relieve the pilot of complying with an ATC clearance, aircraft operating limitations, or other applicable regulations, and an unsafe departure may implicate 14 CFR 91.13.
  • All DPs provide the pilot with a way to depart the airport and transition to the en route structure safely.
  • When evaluating operational and regulatory margins, remember that the FAA evaluates each procedure independently using established TERPS criteria.
    • Combining elements from different procedures creates a flight path that has not been evaluated as a complete procedure.
    • Unless specifically authorized by ATC, this practice may be noncompliant and could compromise obstacle clearance.
Departure Procedures

Departure Procedures References