How to Read and Brief a Textual ODP

When you file and fly an IFR flight plan, the assumption embedded in every clearance is that you can depart the airport safely and climb to your assigned altitude without hitting anything. At many airports, that assumption is backed up by a published Obstacle Departure Procedure (ODP). Unlike a graphic SID (Standard Instrument Departure), many ODPs appear only as lines of text inside the front pages of the FAA Terminal Procedures Publication (TPP) — the same booklet or digital equivalent that contains approach plates. Learning to locate, decode, and brief these textual ODPs is one of the most practical and consistently tested skills in instrument training.

This article walks you through exactly what a textual ODP is, why it exists, how to read every element of it, and how to build a concise cockpit brief so that nothing surprises you during the most critical phase of an IFR flight.

What Is a Textual ODP and Where Do You Find It?

The FAA defines an ODP as a preplanned instrument flight rule (IFR) departure procedure that provides obstruction clearance via the least onerous route from the terminal area to the en route structure. ODPs are published to protect pilots from terrain and obstacles during the initial climb when a radar vector or ATC clearance cannot guarantee that protection. Crucially, ODPs are not clearances — ATC does not routinely issue them. A pilot does not need a separate ATC clearance specifically authorizing the ODP itself to fly it, and in many cases should fly it to remain safe, but the aircraft must still be operating under an appropriate IFR ATC clearance for the flight.

Textual ODPs are found in the "Departure Procedures" section of the TPP, organized alphabetically by state and then by airport name. Each entry begins with the airport identifier and name, then lists one or more runway-specific or all-runway departure descriptions in plain English. You will not see a separate chart for a textual ODP — everything you need is in those few lines of text, which is exactly what makes them easy to overlook and important to study carefully.

Anatomy of a Textual ODP: Reading Every Element

A typical textual ODP entry might read something like this (paraphrased for instruction):

"TAKEOFF MINIMUMS: Rwys 5, 23, 500-1. Rwy 14, NA. DEPARTURE PROCEDURE: Rwy 5, climb heading 052° to 3000 before turning left. Rwy 23, climbing right turn heading 270°, climb to 4000 before proceeding on course. All aircraft, climb in visual conditions to cross SMITH VOR at or above 5000 before proceeding on course."

Let us break down each component systematically.

Takeoff Minimums

Standard FAA takeoff minimums for Part 91 operators are 1 statute mile visibility for single and twin-engine aircraft and 1/2 statute mile for aircraft with more than two engines. When the textual ODP lists non-standard takeoff minimums (for example, "500-1" meaning a 500-foot ceiling and 1 statute mile visibility), those values exceed the standard and exist because of specific obstacles near the departure end of that runway. Part 91 pilots are not legally required to comply with published non-standard takeoff minimums, but ignoring them is dangerous — they are there because obstacle clearance cannot be guaranteed in lower conditions. Part 121 and Part 135 operators are legally required to meet or exceed published non-standard minimums.

"NA" — Not Authorized

When a runway shows "NA" (Not Authorized) in the takeoff minimums section, it means there is no obstacle departure procedure available for that runway and no way to guarantee obstacle clearance during an IFR departure. This may be due to extremely steep terrain, a tall obstacle directly off the departure end, or simply the fact that no procedure has been designed. As a practical matter, departing IFR from an NA runway without specific ATC radar surveillance and a void-time clearance is extremely hazardous and generally should not be attempted.

Climb Heading and Initial Heading

The procedure will specify a magnetic heading to fly immediately after liftoff. This is not a suggestion — it is the precise track that keeps you clear of the obstacles the procedure was designed to avoid. Even a few degrees of deviation can put you outside the protected airspace. Fly the heading as published until the next instruction (usually an altitude or fix) is reached.

Climb Gradient

The standard TERPS obstacle clearance assumption used to evaluate departure paths is a 200 feet per nautical mile (ft/NM) climb gradient (a 40:1 slope), which corresponds roughly to a 3.3% gradient; ODPs are published specifically where this baseline is not sufficient to clear obstacles. When obstacles are more severe, a textual ODP may specify a higher climb gradient — for example, "climb to 3000 at or above 400 ft/NM." This requirement means your aircraft must achieve that performance or you cannot legally and safely execute the procedure. You should verify your aircraft's actual climb performance from the Pilot's Operating Handbook (POH) against the required gradient before departure, factoring in density altitude, weight, and temperature. If your aircraft cannot meet the gradient, you must not use that runway for an IFR departure.

Climb-To Altitude Before Turning

Many textual ODPs include language such as "climb to 4000 before proceeding on course" or "climb to 3000 before turning left." This altitude constraint prevents you from beginning a turn or course change until you have climbed above the obstacle environment. Turning too early can expose you to terrain that the straight-ahead climb path was designed to avoid. This is one of the most important elements to brief and commit to memory before takeoff.

Crossing Fix Requirements

Some procedures require that you cross a specific navaid or fix at or above a designated altitude — for example, "cross SMITH VOR at or above 5000." This type of requirement links your departure to the en route structure and ensures you arrive at the first fix with adequate terrain separation. If you cannot identify the fix or reach the required altitude in time, the procedure is not viable for your operation.

How to Brief a Textual ODP

A proper ODP brief should be completed before engine start or at least well before the runway — not while taxiing or holding short. Use the following framework to ensure nothing is missed.

1. Locate the procedure: Find your airport's entry in the Departure Procedures section of the TPP. Confirm the correct airport identifier and verify the effective date of the publication.
2. Identify your departure runway: ATC assigns runways; weather and wind dictate them. Know which runway you expect to use and read that runway's specific entry. Also read any "all runways" or "all aircraft" clause that applies regardless of runway.
3. Note takeoff minimums: Are they standard or non-standard? If non-standard, what are the ceiling and visibility requirements? Is the runway NA?
4. Write down the initial heading: Confirm you can set this on the heading bug before liftoff. Brief your co-pilot or say it aloud as a self-check.
5. Check the climb gradient: If a non-standard gradient is required, calculate whether your aircraft can meet it. Use your POH climb performance charts and account for current conditions.
6. Note the climb-to altitude: At what altitude can you turn or proceed on course? Brief this as a hard altitude floor, not a soft target.
7. Identify any navaid or fix requirements: Tune and identify any VOR, NDB, or GPS waypoint required. Confirm the fix is in your avionics before departure.
8. Cross-check with your clearance: ATC may assign a different departure than the ODP. If so, seek clarification. Never assume your clearance replaces the ODP's terrain protection unless ATC specifically provides radar vectors from liftoff.

Why Textual ODPs Matter for Safety

The majority of Controlled Flight Into Terrain (CFIT) accidents during IFR departures involve pilots who either did not know an ODP existed, did not brief it, or deviated from it without understanding the consequence. Mountains, ridgelines, towers, and other obstacles are unforgiving of altitude shortfalls. The ODP represents the FAA's careful engineering of the minimum safe path — deviating from it moves you into unanalyzed airspace where obstacle clearance is unknown.

Textual ODPs are particularly easy to miss because they require a deliberate search in a text-heavy document rather than a visual scan of a chart. Building a pre-departure habit of always checking the Departure Procedures section — every flight, every airport — is the single most effective safeguard.

Key Numbers and Rules

• Standard climb gradient: 200 ft/NM (approximately 3.3%)
• Standard takeoff minimums (Part 91): 1 SM visibility for 1-2 engine aircraft; 1/2 SM for 3+ engines
• Non-standard minimums symbol: A triangle with a "T" inside on approach plates signals non-standard takeoff minimums or ODP text exists
• ODP vs. SID: ODPs require no ATC clearance to fly; SIDs do (they are part of the ATC clearance)
• "NA" runway: No IFR departure procedure exists; instrument departures from that runway are not authorized under IFR without specific ATC provisions
• Part 91 vs. 121/135: Part 91 is not legally required to comply with non-standard minimums, but is still bound by obstacle reality

Memory Aid

Use "HMCA" to brief any textual ODP in sequence: Heading (initial departure heading), Minimums (takeoff minimums and gradient), Climb-to altitude (the floor before turning or proceeding), Altitude fix (any crossing requirement at a navaid). Running HMCA before every IFR departure ensures you extract and retain the four critical elements of the procedure.

Common Test Traps

• ODPs require an ATC clearance — FALSE. A published ODP may be flown without a specific ATC clearance. SIDs, by contrast, are part of the ATC clearance and require one.
• Part 91 operators must comply with non-standard takeoff minimums — FALSE. Part 91 is not legally required to do so, but the obstacles that caused those minimums to be published remain real regardless of regulatory category.
• The standard climb gradient is 300 ft/NM — FALSE. The standard is 200 ft/NM. The FAA sometimes lists 400 ft/NM as a non-standard requirement, which makes 200 the commonly tested baseline.
• An NA runway means the ceiling is too low — NOT QUITE. NA means no ODP has been established and obstacle clearance cannot be guaranteed — it is a procedure gap, not just a weather restriction.
• The inverted-T triangle symbol means the approach is complicated — FALSE. That symbol (a triangle containing a "T") specifically flags non-standard takeoff minimums or a published ODP text in the Departure Procedures section, prompting pilots to look it up.