Every IFR departure begins with an implicit promise: that the aircraft can climb away from the airport, navigate through obstacle-laden terrain, and transition safely to the enroute structure — even if something goes wrong immediately after rotation. Engine-out contingency planning within departure procedures is the discipline of thinking through that promise before the takeoff roll begins, not after the propeller stops turning. For instrument-rated pilots, this is not an optional exercise — it is a foundational element of professional flight planning, and it is tested directly on the FAA Instrument Rating knowledge exam.
This article explores how departure procedures are designed, what obstacle clearance guarantees they provide (and what they do not), how a loss of engine power changes the calculus entirely, and how to build a workable engine-out escape plan before every departure.
How Departure Procedures Are Designed
The FAA designs Instrument Departure Procedures (DPs) — both Obstacle Departure Procedures (ODPs) and Standard Instrument Departures (SIDs) — to provide obstacle clearance for aircraft operating on the published procedure. The foundational design standard is a minimum climb gradient of 200 feet per nautical mile (ft/NM) above the departure end of the runway elevation, unless a higher gradient is specifically published. This gradient is calculated for a multi-engine aircraft operating with all engines functioning.
The obstacle evaluation area begins at the Departure End of Runway (DER) — the physical end of the runway or stopway — and expands in a 40:1 slope (roughly 152 ft/NM) outward and laterally. Obstacles that penetrate this imaginary surface must either be avoided by routing the procedure around them or cleared by requiring a steeper climb gradient. The required obstacle clearance (ROC) in the primary area is 48 feet per NM from the DER; ROC does not taper within the primary area itself — rather, it is in the secondary areas that ROC tapers from 48 ft/NM at the inner edge down to zero at the outer edge.
The critical takeaway is this: the obstacle clearance built into a departure procedure assumes normal all-engines-operating performance. The moment one engine fails, all of those calculations become suspect, because obstacle clearance was never designed around single-engine climb performance — at least not explicitly for the departure procedure itself.
The Engine-Out Performance Gap
When an engine fails on a multi-engine aircraft during or immediately after takeoff, several things happen simultaneously: available thrust drops by roughly 50%, but drag increases by far more than 50% due to the asymmetric thrust, windmilling propeller (unless feathered), and the pilot's control inputs to maintain directional control. The net result is that actual single-engine climb performance for most light twins is dramatically lower than published all-engine rates — and in some cases, a light twin may be unable to climb at all below a certain airspeed and configuration.
Single-engine service ceiling for many light piston twins can be surprisingly low — sometimes below 5,000 feet MSL on a warm day at gross weight. If the published departure procedure requires a 300 ft/NM climb gradient and your aircraft's single-engine performance yields only 100 ft/NM, the procedure no longer provides obstacle clearance. This is not a theoretical risk; it is an everyday reality for light twin operations out of mountainous or obstacle-rich airports.
For turbine aircraft and higher-performance twins, FAR Part 25 and 23 certification standards require demonstrated takeoff obstacle clearance performance, but this is measured under controlled conditions with specific assumed engine-failure altitudes. Real-world conditions — density altitude, weight, and aircraft condition — can erode that margin substantially.
Pilot Responsibility for Engine-Out Planning
The FAA places the responsibility for engine-out contingency planning squarely on the pilot in command. The Instrument Procedures Handbook (FAA-H-8083-16) is explicit: a DP provides obstacle clearance only with all engines operating. The PIC must take into account single-engine (or lost-thrust) performance when deciding whether to accept a departure procedure and what escape route is available if an engine fails.
This responsibility involves three distinct tasks:
- Performance review: Before departure, calculate single-engine (or loss-of-thrust) climb performance for the anticipated departure conditions — weight, temperature, pressure altitude, and airport elevation. Determine the actual climb gradient achievable on one engine, and compare it to the required gradient in the DP.
- Obstacle identification: Study the terrain and obstruction environment in the departure corridor. Sectional charts, the airport's departure procedure text, and the Terminal Procedures Publication (TPP) notes all provide relevant information. Identify the critical obstacles and determine at what altitude you would clear them on single-engine performance.
- Escape route selection: Identify a specific course of action for each phase of departure. This means knowing, before you push the throttles, what you will do if the engine fails at 200 feet AGL, at 500 feet, and at 1,000 feet. These decisions cannot be made effectively in the cockpit during the emergency.
Building Your Engine-Out Escape Plan
A practical engine-out escape plan for IFR departure consists of several coordinated elements that should be briefed and committed to memory before takeoff.
Identify Turn and Climb Priorities
The first priority after an engine failure at low altitude is aircraft control — maintaining airspeed at Vyse (best single-engine rate of climb speed), feathering the failed engine promptly, and establishing a wings-level or coordinated bank. Turns into obstructions or into rising terrain are the primary killer in engine-out departures. Your escape route should prioritize turning away from terrain and toward open, low-lying areas wherever possible.
Use Published ODP Climb Gradients as a Benchmark
If the airport has a published ODP with a standard 200 ft/NM gradient, use that as your benchmark. If your single-engine performance meets or exceeds 200 ft/NM at departure weight and conditions, then the published ODP provides a viable path. If your single-engine climb falls short of the published gradient, you must identify terrain that can be avoided by other means — a different departure direction, a lower-gradient ODP option, or delaying departure until conditions improve (lower temperature, reduced weight).
Coordinate With ATC — But Don't Rely on It
ATC can provide radar vectors and clearance amendments during an emergency, but in the critical seconds and minutes after an engine failure at low altitude, the pilot cannot wait for ATC instructions. Your escape route must be pre-planned and pre-briefed so that execution is instinctive. Declare the emergency, squawk 7700, and communicate when the aircraft is under control — not before.
Brief Your Co-Pilot or Passengers
In multi-crew operations, the engine-out escape route must be briefed to the co-pilot as part of the departure briefing. In single-pilot operations, a self-briefing that articulates the plan aloud helps commit the key actions to working memory under stress.
Key Numbers and Rules
- Standard minimum climb gradient: 200 ft/NM above the departure end of runway elevation, unless a higher gradient is charted.
- Obstacle clearance slope: 40:1 (approximately 152 ft/NM), which the departure procedure is designed to exceed.
- Required obstacle clearance (ROC): 48 feet per NM in the primary area of a departure procedure, tapering from 48 ft/NM to zero across the secondary area.
- Vyse: Best single-engine rate-of-climb airspeed — must be known and achievable immediately after engine failure; it is the speed that maximizes climb on one engine.
- Vxse: Best single-engine angle-of-climb speed — used when obstacle clearance is critical and the aircraft must climb steeply over a close-in obstruction, at the cost of a lower climb rate.
- Engine-out ceiling: Know your aircraft's published single-engine service ceiling for the departure conditions; if terrain exceeds this altitude along the departure route, the route is not viable on one engine.
- Takeoff alternate: If the weather at the departure airport is below certain minimums (for 14 CFR Part 91 IFR, generally when ceiling and visibility make a return impossible safely), consider whether a takeoff alternate is appropriate for planning purposes.
Common Test Traps
- Assuming the ODP guarantees obstacle clearance on one engine. It does not. Published departure procedures are designed for all-engines-operating performance. Single-engine obstacle clearance is the PIC's responsibility.
- Confusing Vyse and Vxse. Vyse gives the best rate of climb on one engine (most altitude gained per unit of time), while Vxse gives the best angle (most altitude per unit of horizontal distance). Vxse is used near close-in obstacles; Vyse is used when the goal is maximum altitude gain in cruise climb. Both appear on the knowledge test.
- Ignoring density altitude effects on single-engine performance. The AFM single-engine climb data is often given at standard conditions. On a hot, high-density-altitude day, actual performance can be dramatically worse. Always correct for temperature and elevation.
- Believing ATC is responsible for obstacle clearance during departure. Once a pilot accepts a clearance and departs, obstacle clearance below the minimum vectoring altitude (MVA) or minimum IFR altitude is the pilot's responsibility, not ATC's, unless specifically on a radar departure with vectors.
- Not identifying the escape route before departure. The FAA expects pilots to have a defined plan for engine failure on departure. Vague intentions like "I'll turn left" are not sufficient. Know the specific heading, altitude targets, and terrain considerations for your airport and runway in use.
Engine-out contingency planning is one of the places where instrument flying transitions from procedure-following to genuine airmanship. The charts, gradients, and performance numbers are all tools — but the pilot who understands why those tools exist, and what they cannot protect against, is the pilot who brings every flight to a safe conclusion.