ODPs vs. SIDs: The Diverse Departure, the Trouble T, Climb Gradient Math, VCOA, and Climb Via
Updated: Sep 29
Departing safely under Instrument Flight Rules requires more than flying runway heading and climbing. Terrain, obstacles, airspace complexity, and traffic flow all influence how an aircraft transitions from the runway to the enroute structure. Two key tools manage this phase: Obstacle Departure Procedures (ODPs) and Standard Instrument Departures (SIDs). Although they serve different purposes, they're often confused or used interchangeably — and the real understanding lives in the details underneath them: the "diverse departure" assumptions every IFR departure is built on, the little "T" on the approach plate that tells you an ODP exists, the math that converts a published climb gradient into a rate you can actually fly, and what your options are when you can't meet it.
This post covers instrument departures in practical depth: the diverse departure standard everything is built on, what ODPs are and how you find them (the Trouble T), Part 91 takeoff minimums, SIDs and the climb-via phraseology, the climb gradient conversion math with a worked example, VCOA and other options when you can't meet a gradient, diverse vector areas, pilot responsibilities, and the checkride questions — with answers.
Study this full length lesson (video, podcast, flashcards, and quiz) here: Full Length Lesson >
The Foundation: The Diverse Departure Assumptions
Before ODPs and SIDs make sense, you need the standard they're built on. Every IFR departure procedure assumes a set of "diverse departure" criteria — and when an airport can't meet them, that's when an ODP is born.
The standard assumptions (what the designers assume you'll do):
Cross the departure end of the runway (DER) at least 35 feet AGL
Climb to 400 feet above the airport elevation before turning (on runway heading)
Maintain a climb gradient of at least 200 feet per nautical mile to the minimum IFR altitude
If you do these things, the procedure guarantees obstacle clearance
Why these specific numbers:
35 feet at the DER: a minimum screen height above the runway end
400 feet before turning: keeps you climbing straight ahead through the initial obstacle-clearance zone
200 ft/NM: the standard climb gradient that clears obstacles beneath a standard obstacle surface (below)
The baseline everyone designs to
The "diverse departure" concept:
If NO obstacles penetrate the standard obstacle surface, the airport qualifies for a "diverse departure"
That means you can depart in ANY direction (diverse) after reaching 400 feet, climbing at 200 ft/NM, and be clear of obstacles
No special procedure needed
The airport is "clean"
When the assumptions fail:
If an obstacle penetrates the surface, a diverse departure isn't possible
Something must be published to keep you clear
That something is an ODP (or a note on takeoff minimums)
The trigger for everything that follows
The 40:1 Obstacle Identification Surface
The geometric standard behind the 200 ft/NM number.
The 40:1 surface:
An imaginary sloping surface rising from the departure end of the runway
It rises 1 foot for every 40 feet of horizontal distance
That works out to 152 feet per nautical mile (6,076 ÷ 40 ≈ 152)
The "obstacle identification surface" (OIS)
How it's used:
Designers check whether any obstacle penetrates (sticks up through) the 40:1 surface
If nothing penetrates: diverse departure, standard 200 ft/NM works
If something penetrates: an ODP or non-standard takeoff minimums are required
The screening tool
Why 200 ft/NM (not 152):
The surface rises at 152 ft/NM
The required climb is 200 ft/NM
The difference (48 ft/NM) is the built-in obstacle-clearance MARGIN
So flying 200 ft/NM keeps you comfortably above a 152 ft/NM surface
When a steeper gradient is published:
If an obstacle penetrates the 40:1 surface, the designers compute the gradient needed to clear it (with margin)
They publish that steeper gradient (e.g., 350 ft/NM to 3,000 feet)
Or they publish a turn/routing that avoids the obstacle
Or both
The takeaway:
40:1 = 152 ft/NM is the obstacle surface
200 ft/NM is the standard climb (with margin)
A penetration produces an ODP and/or a higher published gradient
The geometry behind the procedure
What an Obstacle Departure Procedure (ODP) Is
An ODP is a published IFR procedure designed SOLELY to ensure obstacle clearance after takeoff.
Purpose of an ODP:
Protect aircraft from terrain and man-made obstacles
Provide a safe path from the runway to a point where standard IFR navigation can begin
Account for obstacles that can't be cleared using the standard 200 ft/NM diverse departure
Obstacle clearance, and nothing else
When ODPs are created:
When obstacles penetrate the 40:1 obstacle identification surface, OR
When a climb gradient greater than 200 ft/NM is required
Either condition means the diverse departure doesn't work
The airport needs a published solution
Key characteristics:
Obstacle avoidance only (NOT traffic flow)
Often simple in design (a heading, a turn at an altitude, a gradient)
May require: specific headings, turns at defined altitudes, higher-than-standard climb gradients, or a specific routing to a fix
Does NOT require an ATC clearance to fly (unless ATC assigns something else)
The "no clearance needed" point (important):
An ODP is the pilot's tool — you fly it on your own initiative for obstacle clearance
Unlike a SID, it's not assigned in your clearance as a matter of course
You're expected to fly it when it applies, unless ATC gives you an alternative (vectors, a SID)
Your responsibility
Where ODPs are published:
Textual ODPs — in the "Takeoff Minimums, (Obstacle) Departure Procedures, and Diverse Vector Area" section at the front of the Terminal Procedures Publication (TPP), listed alphabetically by airport
Graphic ODPs — charted like a SID, but titled "(OBSTACLE)" in the procedure name (e.g., "CHEYENNE THREE (OBSTACLE)")
If a graphic ODP exists, it replaces the textual version for that runway
The textual ODP format:
Written as text: "Rwy 27, climbing right turn to 3000 direct XYZ VOR before proceeding on course" or "Rwy 9, std. w/min. climb of 280' per NM to 4000"
Read it carefully — the wording is precise
Often includes runway-specific notes
Easy to skim past; don't
The Trouble T: How You Know an ODP Exists
Here's the single most practical detail the original doesn't cover: the symbol that tells you to go look.
The "T" symbol (the "Trouble T"):
On an instrument approach chart, look for a black triangle with a white "T" inside in the notes/briefing strip
It means: non-standard takeoff minimums and/or an ODP exist for this airport
It's your cue to look up the Takeoff Minimums and ODP section of the TPP
Nicknamed the "Trouble T"
What it does NOT tell you:
It doesn't say WHAT the minimums or ODP are — only that they exist
You must go to the front of the TPP (or your EFB's takeoff minimums page) to read them
The T is a pointer, not the content
Follow the pointer
The A symbol (companion):
A triangle with an "A" means non-standard ALTERNATE minimums (a different topic)
Don't confuse the two
T = takeoff/ODP; A = alternate
Both are "go look it up" flags
The practical habit:
During preflight for any IFR departure, check the approach charts for the departure airport for the T
If present, read the takeoff minimums and ODP
Brief the ODP (and confirm you can meet any climb gradient)
Even if the airport has a SID, the ODP information (and gradient) may still matter
Why it's easy to miss:
It's a small symbol
Pilots focused on the destination forget the departure
The ODP isn't in your clearance
The T is your reminder
Part 91 Takeoff Minimums: The Legal Reality
An important regulatory point the original touches on but doesn't state.
The Part 91 rule:
For Part 91 operators, there are NO legally required takeoff minimums — you can legally depart IFR in zero-zero
The published takeoff minimums (e.g., "300-1") apply to Part 121, 125, 129, and 135 operators
Part 91 is legally free to ignore them
(Standard minimums for those commercial operators: 1 SM visibility for 1-2 engines, ½ SM for 3+ engines, unless non-standard minimums are published)
The AIM's strong recommendation:
The AIM strongly encourages Part 91 pilots to use the published takeoff minimums and to fly the ODP
Especially at night, in IMC, or in marginal VMC
Legal freedom is not the same as safe practice
Use them
Why Part 91 pilots should follow ODPs anyway:
The obstacle is still there whether the regulation binds you or not
Departing into IMC without the ODP means you've abandoned the only published obstacle-clearance guarantee
Terrain doesn't check your operating rules
Fly the ODP
The night/IMC emphasis:
In daylight VMC, you can see and avoid obstacles (the ODP is less critical)
At night or in IMC, you can't — the ODP is your only protection
This is where ODPs earn their keep
Non-negotiable in the dark
What a Standard Instrument Departure (SID) Is
A SID is a published IFR procedure designed to manage traffic flow, airspace complexity, and ATC workload — while also providing obstacle clearance.
Purpose of a SID:
Streamline departures from busy airports
Reduce radio congestion (a whole routing in one clearance)
Ensure predictable aircraft routing
Integrate departing aircraft into the enroute system efficiently
Obstacle clearance is INCLUDED, but it's not the primary purpose
Key characteristics:
Designed for ATC efficiency
Often complex and multi-page
May include: multiple transitions, speed restrictions, altitude constraints, RNAV routing, or radar vectors
REQUIRES an ATC clearance to fly (it's assigned)
The two flavors of SID:
Pilot-navigation SIDs: you navigate the published route yourself (via VORs, fixes, or RNAV)
Vector SIDs: ATC provides radar vectors to the enroute structure; the chart depicts the initial headings/altitudes and where vectors take over
Know which type you've been assigned
Different workload
The "as published" expectation:
If ATC assigns a SID, fly it EXACTLY as published unless otherwise instructed
Every altitude, speed, and turn point
ATC is sequencing traffic around your predicted path
Precision matters
Declining a SID:
You may file "NO SID" in your flight plan remarks if you don't want one (or can't comply)
ATC will then provide an alternative (usually vectors)
You still need obstacle clearance (the ODP or vectors in a DVA)
An option, not a loophole
"Climb Via" and the Top Altitude
Modern SID phraseology the original doesn't cover — and a source of real confusion.
The "climb via" clearance:
ATC may say "Climb via the [NAME] departure"
This means: fly the SID's lateral route AND comply with ALL its published altitude and speed restrictions
Climbing to the SID's published TOP ALTITUDE
One phrase authorizes the whole vertical profile
The top altitude:
Every "climb via"-eligible SID has a published top altitude (on the chart, often in a box)
That's the altitude you climb to unless ATC amends it
"Climb via" without a stated altitude = climb to the top altitude
Know it before you go
"Climb via except maintain":
"Climb via the [NAME] departure, except maintain 8,000" — fly the restrictions, but level at 8,000 instead of the top altitude
The "except" modifies only the final altitude
All intermediate restrictions still apply
A common variant
"Climb and maintain" (the older form):
"Climb and maintain 5,000" WITHOUT "climb via" means: climb to 5,000, and the SID's published altitude restrictions are CANCELED (but the lateral route and speed restrictions still apply, unless ATC says otherwise)
The distinction between "climb via" and "climb and maintain" is exactly this: whether the published altitude restrictions apply
A frequent readback/compliance error
Listen carefully
The read-back:
Read back "climb via" clearances exactly ("Climb via the [NAME] departure")
If given a top altitude or "except maintain," read it back
Confirms mutual understanding
Standard practice
Climb Gradients: The Math You Actually Need
Both ODPs and SIDs may require climb gradients greater than 200 ft/NM — and a gradient in feet per NAUTICAL MILE isn't something you can fly directly. You need feet per MINUTE.
Why the conversion is needed:
Published gradients are in feet per nautical mile (ft/NM) — distance-based
Your VSI reads feet per minute (fpm) — time-based
The link between them is your GROUNDSPEED
Convert before you fly
The formula:
Required rate (fpm) = climb gradient (ft/NM) × groundspeed (knots) ÷ 60
(Because at X knots you cover X NM per hour, or X/60 NM per minute)
Multiply, then divide by 60
Simple once you've done it once
A worked example:
Published gradient: 350 ft/NM to 4,000 feet
Planned climb groundspeed: 90 knots
350 × 90 = 31,500
31,500 ÷ 60 = 525 fpm
You must sustain at least 525 fpm (at 90 kt groundspeed) until 4,000 feet
The groundspeed catch:
A TAILWIND increases groundspeed → you need a HIGHER fpm to hold the same gradient
A headwind helps (lower fpm needed)
Use groundspeed, not airspeed
At 120 kt groundspeed in the example above: 350 × 120 ÷ 60 = 700 fpm
The climb gradient table:
The TPP includes a "Rate of Climb/Descent Table" (and many charts print a mini-table) converting gradient to fpm at various groundspeeds
Use it to cross-check your math
On the chart or in the front of the book
A ready reference
The performance check:
Can your aircraft ACTUALLY produce that rate at that weight, density altitude, and temperature — all the way to the specified altitude?
Check the POH climb performance charts
A normally-aspirated single on a hot day at a high-elevation airport may NOT make 525 fpm
Verify before departure, not after
"Published climb gradients are not advisory":
They're the minimum required to clear the obstacle with margin
Failing to meet one means you may not clear the obstacle
Not a suggestion
Treat it as a hard requirement
When You Can't Meet the Climb Gradient
The original asks this as a checkride question but doesn't answer it. Here are the options.
Option 1 — Don't depart (or wait):
If the required gradient exceeds your aircraft's capability, the honest answer may be "not today" or "not at this weight"
Wait for cooler temperatures (better performance)
The safest option
Sometimes the only option
Option 2 — Reduce weight:
Less fuel (if range allows), fewer passengers, less baggage
Improves climb performance
May bring the required rate within reach
Recalculate
Option 3 — Use a different runway:
The gradient is often runway-specific
Another runway may have a standard (200 ft/NM) departure or a lower gradient
Check the ODP for each runway
Depart on the easier one (if winds allow)
Option 4 — VCOA (Visual Climb Over Airport):
Some ODPs offer a VCOA as an alternative to the steep gradient
You climb VISUALLY in a spiral over the airport (staying within a specified radius) until reaching a specified altitude, THEN proceed on course
This lets you climb at your own rate — in VMC over the airport — before heading toward the obstacle
Requires the published VCOA weather minimums (ceiling and visibility to keep the airport in sight)
How VCOA works:
Published as: "VCOA: Obtain ATC approval for climb in visual conditions when requesting IFR clearance. Climb in visual conditions to cross [airport] at or above [altitude], then proceed on [course]"
You must REQUEST it from ATC when getting your clearance
Circle over the airport in visual conditions until at the published altitude
Then depart on course, now above the obstacle problem
When VCOA is useful:
Lower-performance aircraft that can't meet a steep gradient
When the weather allows visual climbing over the airport but IMC exists en route
A legitimate, published alternative
Read the ODP for VCOA availability
Option 5 — Depart VFR and pick up IFR airborne:
If the weather allows a VFR departure, climb visually (seeing and avoiding obstacles), then get your IFR clearance airborne
Only if you can maintain VFR until clear of obstacles and until receiving the clearance
Requires solid VMC and an escape plan
Not an option in IMC
The wrong answer:
"I'll just fly the standard 200 ft/NM and hope" — no
The gradient is published because 200 won't clear the obstacle
Meet it, or use one of the options above
Never guess
Diverse Vector Areas (DVA): Why Vectors Can Substitute
A concept that explains how ATC can vector you without an ODP.
What a DVA is:
A Diverse Vector Area is airspace around an airport where ATC has evaluated obstacle clearance for radar vectors
Within it, ATC can vector departures below the minimum vectoring altitude, and obstacle clearance is assured by the DVA design
Published in the same TPP section as ODPs ("...and Diverse Vector Area")
Lets vectors replace the ODP
How it's used:
ATC says "fly runway heading" or "turn left heading 270" right after departure
If a DVA exists, those vectors provide obstacle clearance (ATC has done the analysis)
You comply with the vectors and don't need the ODP's routing
The vector IS your obstacle clearance
The climb gradient still applies:
A DVA may have its own published climb gradient (often the standard 200 ft/NM, sometimes higher)
Check the DVA note in the TPP
Vectors handle the ROUTING; you still handle the CLIMB
Both parts
If no DVA exists:
ATC still may vector you, but you're responsible for terrain/obstacle awareness until reaching the minimum vectoring altitude
The ODP is your obstacle-clearance plan
Know whether your airport has a DVA
Check the TPP
Pilot Responsibilities and Common Pitfalls
The responsibilities, expanded.
For ODPs:
Look them up PROACTIVELY (the Trouble T is your cue)
They're NOT automatically included in your clearance — "cleared as filed" does not include the ODP
Easy to overlook during preflight planning (the destination gets the attention)
Especially critical at night or in IMC
If ATC gives you vectors or a SID instead, that replaces the ODP; if not, fly it
The "cleared as filed" trap:
Your clearance may not mention the ODP at all
That does NOT mean it doesn't apply
You're expected to fly it (or a SID/vectors) for obstacle clearance
Silence isn't waiver
For SIDs:
Ensure the aircraft is properly EQUIPPED (RNAV capability, DME, GPS with the required certification)
Ensure you're FAMILIAR with the procedure (brief it)
Brief altitude and speed restrictions carefully
Understand "climb via" vs. "climb and maintain"
Risk of deviation is higher due to complexity
The RNAV equipment note:
Many modern SIDs (and some ODPs) are RNAV-based
Require GPS with appropriate certification (and the right equipment code filed — see the flight-plan post)
Precise lateral paths, reduced reliance on vectors
Don't accept an RNAV SID you can't fly
The briefing habit (either procedure):
Initial heading and altitude
Any turn points and the altitude to reach before turning
The climb gradient (converted to fpm at your groundspeed) and your aircraft's capability
The top altitude (SID) or the altitude at which the ODP ends
Lost-communications plan
Checkride Questions — With Answers
The original lists the questions; here are the answers.
"What's the difference between an ODP and a SID?"
An ODP exists solely for obstacle clearance; you fly it on your own initiative, and it doesn't need an ATC clearance
A SID exists primarily for ATC traffic flow (with obstacle clearance built in); it's assigned by ATC and requires a clearance
ODPs keep you from hitting something; SIDs keep traffic flowing
"When must you fly an ODP?"
Legally, Part 91 isn't required to — but when one exists and you're departing IFR (especially at night or in IMC), you're expected to fly it unless ATC provides an alternative (a SID or vectors in a DVA)
Commercial operators (121/135) are required to comply with published departure procedures and takeoff minimums
Practically: fly it whenever you can't see and avoid the obstacles yourself
"Can ATC assign an ODP?"
YES — ATC can assign an ODP in your clearance (e.g., "fly the [NAME] obstacle departure" or by including the textual ODP routing)
More commonly, ATC assigns a SID or vectors, and the ODP is the pilot's own tool
If assigned, it's part of your clearance and you fly it as instructed
Either way, you can always fly it on your own initiative
"What if you can't meet the climb gradient?"
Don't depart until you can (wait for better conditions), reduce weight, use a different runway with a lower gradient, use a VCOA if published, or depart VFR and pick up IFR airborne if the weather allows
The one thing you can't do is fly the standard 200 ft/NM and hope
The gradient exists because 200 won't clear the obstacle
"How do you convert a climb gradient to a rate?"
Gradient (ft/NM) × groundspeed (kt) ÷ 60 = fpm
350 ft/NM at 90 kt = 525 fpm
Use groundspeed (tailwinds raise the required rate)
"How do you know an ODP exists?"
The Trouble T (black triangle, white T) on the approach charts for the airport
Then read the Takeoff Minimums and ODP section of the TPP
Conclusion
While both Obstacle Departure Procedures and Standard Instrument Departures guide aircraft safely away from the runway, they serve very different roles: ODPs exist to keep you from hitting something; SIDs exist to keep traffic flowing smoothly. Both are built on the diverse-departure standard — 35 feet at the DER, 400 feet before turning, 200 feet per nautical mile — and both can demand more than that when terrain intrudes.
The practical skill is in the details: spotting the Trouble T and reading the ODP even when your clearance doesn't mention it, converting a published climb gradient into a rate you can actually fly at your groundspeed (and confirming your aircraft can produce it), understanding "climb via" and the top altitude on a SID, and knowing your options — a different runway, less weight, a VCOA, or simply waiting — when the gradient is beyond you. Understanding when and how to use each procedure, and your responsibilities as the pilot, ensures safe, compliant, and professional IFR operations.
On the Written Test and Checkride
Departure procedures appear on tests and checkride orals (instrument especially). The most commonly tested topics:
The difference between an ODP (obstacle clearance) and a SID (traffic flow)
The diverse departure assumptions (35 ft at DER, 400 ft before turning, 200 ft/NM)
The 40:1 obstacle identification surface (152 ft/NM)
The Trouble T symbol and where ODPs are published
Part 91 takeoff minimums (none required, but recommended)
Climb gradient conversion (ft/NM × groundspeed ÷ 60)
"Climb via" vs. "climb and maintain"
VCOA and options when you can't meet a gradient
Quick Reference
Diverse Departure Assumptions (the standard):
Cross the DER at ≥ 35 ft AGL
Climb to 400 ft above airport elevation before turning
Climb ≥ 200 ft/NM to the minimum IFR altitude
If no obstacle penetrates the 40:1 surface → diverse departure (any direction after 400 ft)
The 40:1 Surface:
Rises 1 ft per 40 ft horizontal = 152 ft/NM
200 ft/NM standard climb = 152 + 48 ft/NM margin
A penetration → ODP and/or higher gradient
ODP (Obstacle Departure Procedure):
Purpose: obstacle clearance ONLY
Created when obstacles penetrate the 40:1 surface or > 200 ft/NM is needed
Simple: headings, turns at altitudes, gradients, routing to a fix
Does NOT require an ATC clearance (pilot's tool) — but ATC CAN assign one
Published: textual (TPP Takeoff Minimums/ODP section) or graphic (titled "(OBSTACLE)"; replaces textual)
NOT included in "cleared as filed" — you must look it up
The Trouble T:
Black triangle with white "T" on the approach charts
Means non-standard takeoff minimums and/or an ODP exist
Go read the TPP Takeoff Minimums/ODP section
(Triangle "A" = non-standard ALTERNATE minimums — different)
Part 91 Takeoff Minimums:
No legal takeoff minimums for Part 91 (legal in zero-zero)
Published minimums bind Part 121/125/129/135 (std: 1 SM for 1-2 engines, ½ SM for 3+)
AIM strongly encourages Part 91 to use them and fly the ODP — especially at night/IMC
SID (Standard Instrument Departure):
Purpose: ATC traffic flow (obstacle clearance included)
Complex: transitions, speed/altitude restrictions, RNAV or vectors
REQUIRES an ATC clearance (assigned)
Pilot-nav SIDs (you navigate) vs. vector SIDs (ATC vectors)
Fly exactly as published; file "NO SID" to decline
Climb Via:
"Climb via the [NAME] departure" = fly the route AND all published altitude/speed restrictions to the TOP ALTITUDE
"Climb via... except maintain X" = restrictions apply, level at X
"Climb and maintain X" (no "climb via") = published ALTITUDE restrictions canceled; route and speeds still apply
Read back exactly
Climb Gradient Conversion:
fpm = gradient (ft/NM) × groundspeed (kt) ÷ 60
Example: 350 ft/NM at 90 kt = 525 fpm; at 120 kt = 700 fpm
Use GROUNDSPEED (tailwind raises the required rate)
Verify the POH can deliver it (weight, density altitude, temperature)
Published gradients are NOT advisory
Can't Meet the Gradient?
Don't depart / wait for better conditions
Reduce weight
Use a different runway (gradient is runway-specific)
VCOA (Visual Climb Over Airport) if published — request from ATC, spiral visually over the airport to the published altitude, then proceed
Depart VFR, pick up IFR airborne (VMC only)
Never fly 200 ft/NM and hope
Diverse Vector Area (DVA):
Airspace where ATC-evaluated radar vectors provide obstacle clearance
Vectors can replace the ODP's routing
May have its own climb gradient (check the TPP)
No DVA → you own terrain awareness until the MVA
Key Principle:
ODPs keep you from hitting something (obstacle clearance, pilot's tool, no clearance needed); SIDs keep traffic flowing (ATC's tool, assigned, "climb via" to the top altitude). Both rest on the diverse-departure standard — 35 ft at the DER, 400 ft before turning, 200 ft/NM. Spot the Trouble T, read the ODP even when your clearance is silent, convert the gradient to fpm at your groundspeed (gradient × GS ÷ 60), and if you can't make it, wait, lighten up, change runways, or fly the VCOA.
Study Full Aviation Courses:
wifiCFI's full suite of aviation courses has everything you need to go from brand new to flight instructor and airline pilot! Check out any of the courses below for free:
Study Courses:
Checkride Lesson Plans:
Teaching Courses:
Author: Nathan Hodell
CFI, CFII, MEI, ATP, Creator and CEO
Nathan is an aviation enthusiast with thousands of hours of flying and dual instruction over the past 15+ years. Through his aviation career he has been able to earn his ATP, fly as an airline pilot, own/operate flight schools, and create and host wifiCFI.