Outcome 7.14 Emergency Operations — Practical Decision-Making for Single- and Multiengine Pilots

7.14.1 Describe emergency operations

Emergency operations are the procedures and decision-making habits you use when an abnormal or unsafe situation threatens the flight—anything from an engine failure to smoke in the cockpit to a landing gear malfunction. What makes an “emergency” different from a routine abnormality is time pressure and risk: you may have only seconds to stabilize the aircraft and choose the safest outcome.

The core priority: control first, then decisions

A reliable way to think under stress is the classic priority order Aviate–Navigate–Communicate:

  • Aviate: keep the aircraft under control—attitude, airspeed, configuration, and flight path.
  • Navigate: put the aircraft where it needs to be—toward an airport, suitable landing area, or safe altitude/airspace.
  • Communicate: tell others what you need—ATC, passengers, other crew—and activate emergency services.

This order matters because many accidents happen when pilots “go heads-down” troubleshooting and let airspeed decay, allow an unusual attitude, or drift into terrain/airspace. You can almost always delay troubleshooting for a few seconds to stabilize the airplane.

“Diagnose less, do more”: checklists and flows

In real emergencies, perfect diagnosis is often less important than executing memory items that immediately reduce risk (for example, reducing power in an engine fire, or lowering the nose in a stall). After immediate actions, you transition to:

  • A flow (a consistent scan pattern across cockpit controls)
  • Then a checklist (to verify you didn’t miss anything)

A common mistake is using a checklist as the first step while the situation is still rapidly changing. The checklist is there to confirm, not to replace aircraft control.

Declaring an emergency and using all resources

If you need priority handling, do not hesitate to declare an emergency with ATC. In the U.S., the pilot in command has broad authority to deviate from rules as required to meet an emergency—what matters is that you can justify your actions as necessary for safety. Practically, declaring early can get you:

  • Priority routing and traffic separation
  • Runway selection and emergency equipment standing by
  • Weather, NOTAM, and airport condition information

Also use cockpit resources: autopilot (if functioning), passenger help (look for traffic, read checklist), and onboard equipment (GPS nearest function, moving map, terrain alerts).

Exam Focus
  • Typical question patterns:
    • Scenario: “You have smoke/roughness/fuel smell—what are your immediate priorities and next actions?”
    • “When should you use memory items vs the checklist?”
    • “When is it appropriate to declare an emergency and what are the benefits?”
  • Common mistakes:
    • Troubleshooting before stabilizing airspeed/attitude.
    • Waiting too long to declare—losing options and time.
    • Fixating on “saving the airplane” instead of choosing the lowest-risk outcome.

7.14.2 Demonstrate emergency descent

An emergency descent is a rapid reduction in altitude used when staying at the current altitude is more dangerous than descending. Common triggers include cabin smoke/fire, loss of pressurization (if applicable), engine roughness requiring immediate landing, or icing conditions that demand a lower, warmer layer.

Why emergency descents are tricky

Descending quickly increases workload and risks:

  • Overspeed (exceeding structural limits)
  • Shock cooling concerns in some piston operations (less important than survival in true emergencies, but still something to manage when time allows)
  • Spatial disorientation and high sink rates close to terrain
  • Traffic conflicts if you descend without coordination

So your goal is maximum safe rate of descent—not simply “as fast as possible.” You control descent rate primarily with pitch, and you manage airspeed with pitch and configuration.

How it works (generic technique—always follow the POH)

Different aircraft have different approved techniques, but a typical emergency descent profile looks like this:

  1. Clear the area (quick visual scan; if IMC, rely on instruments/ATC as available).
  2. Reduce power (often to idle) to help prevent overspeed.
  3. Set a safe high airspeed (below redline and within aircraft limitations). Many aircraft use a “high-but-allowed” speed range for best descent rate.
  4. Increase drag if approved (speed brakes, flaps/gear only if the POH allows it at that speed and it helps without exceeding limits).
  5. Use a banked descending turn if appropriate (a moderate bank can increase descent rate while keeping speed manageable—but steep banks raise stall speed and increase disorientation risk).
  6. Level off early to avoid high-speed proximity to terrain and to prevent ballooning/over-G.
Example: smoke in the cockpit

If smoke increases rapidly, your immediate “aviate” goal is to get to breathable air and a landing environment:

  • Start descent while simultaneously addressing the source (ventilation, electrical load shedding) if you can do so without losing control.
  • Communicate with ATC as soon as practical; a quick call like “declaring emergency, smoke in cockpit, descending” may be all you can manage initially.

Common error: starting a steep spiral descent without a plan for rollout altitude—leading to overspeed or terrain/obstacle risk.

Exam Focus
  • Typical question patterns:
    • “What situations justify an emergency descent, and what are the main risks?”
    • “Describe a safe sequence for an emergency descent.”
    • Scenario: “You’re in IMC and need to descend rapidly—what do you prioritize?”
  • Common mistakes:
    • Exceeding airspeed or flap/gear limits.
    • Fixating inside the cockpit and failing to manage terrain/traffic.
    • Leveling off too late, resulting in altitude busts or high-speed close to the ground.

7.14.3 Solve non-routine problems during emergency approach and landing (ASEL, ASES)

For single-engine airplane land (ASEL) and single-engine sea (ASES) operations, the emergency approach and landing phase is where planning meets physics: once you commit to a landing area, you have limited ability to “fix” a bad setup.

The big idea: energy management

In an emergency approach, you manage two forms of energy:

  • Potential energy (altitude)
  • Kinetic energy (airspeed)

With an engine-out in a single, altitude is your “bank account.” Spending it too early (getting low and slow) removes options; spending it too late (arriving high and fast) can force an unstable approach.

ASEL: selecting a landing site and building a pattern

A disciplined approach is:

  1. Choose the most survivable site (airport if reachable; otherwise field/road only if suitable—avoid obstacles, wires, and confined areas).
  2. Fly a predictable pattern (many pilots use a modified downwind/base/final to avoid tight turns at low altitude).
  3. Use checklists when time allows (restart attempts, fuel selector, mixture, ignition, carb heat/alternate air—per aircraft).
  4. Aim point discipline: pick a touchdown point early and hold it visually.
  5. Configure late enough to avoid coming up short (flaps are a tool to steepen the approach; they are not a “fix” for being low).

A frequent mistake is turning base too low or tightening the turn to final—leading to an overshoot and a stall/spin risk.

ASES: what changes on water

In a seaplane, “landing area selection” includes water surface condition and landing attitude cues:

  • Glassy water can remove depth perception and visual sink cues, encouraging pilots to flare too high and stall.
  • Rough water can demand a different technique to prevent porpoising or digging a float.

If you’re forced to land on water, you plan for:

  • Wind and swell direction (when discernible)
  • Obstacles (boats, buoys, submerged hazards near shore)
  • Post-landing survival (temperature, drift toward hazards, ability to exit)

In both ASEL and ASES, your emergency approach should aim for a stable final—consistent airspeed, descent rate, and alignment—because “saving” an unstable approach near the surface is where loss-of-control accidents happen.

Exam Focus
  • Typical question patterns:
    • Scenario: “Engine failure—describe how you set up an emergency landing pattern.”
    • “How do flaps help/hurt during an emergency approach?”
    • “What special hazards exist for emergency water landings?”
  • Common mistakes:
    • Stretching a glide (raising the nose) instead of accepting the best glide attitude.
    • Tight, skidding turns close to the ground.
    • Configuring too early and arriving short of the intended touchdown area.

7.14.4 Describe systems and equipment malfunctions

A systems malfunction is any failure or abnormal behavior of aircraft components that support flight—engine, fuel, electrical, flight controls, landing gear, pitot-static/instruments, and environmental systems. The best way to handle these is to understand what the system does and what “backup modes” exist.

Engine and fuel system issues

Many “engine problems” are actually fuel/air/ignition delivery problems. Your troubleshooting logic should be simple and prioritized:

  • Power loss: confirm fuel (selector, quantity indication skepticism), mixture, carb heat/alternate air, ignition (magnetos), and engine instruments.
  • Rough running: consider fuel contamination, improper mixture, induction icing, or ignition problems.

Don’t chase perfect diagnosis at low altitude. If power is not reliably available, move toward landing.

Electrical failures

An electrical malfunction can range from a nuisance (failed radio) to a serious emergency (electrical fire). Key concepts:

  • The alternator/generator supplies power; the battery provides reserve.
  • Load shedding (turning off nonessential equipment) can preserve essential avionics.
  • Electrical smoke/fire often demands aggressive action—de-energize suspect systems and ventilate per POH.

Common error: continuing with unnecessary loads until the battery is exhausted, then losing flaps, radios, or gear extension assistance (aircraft-dependent).

Pitot-static and instrument failures

If pitot or static sources are blocked, airspeed and altitude indications can become unreliable. The practical skill is recognizing instrument disagreement:

  • Airspeed behaving oddly compared to pitch/power
  • Altimeter and vertical speed anomalies
  • Indicated changes that do not match outside references

Use known pitch/power settings and cross-check other cues (GPS groundspeed trend, attitude, engine power) while following the POH for alternate static source use if installed.

Flight control and landing gear/flap malfunctions
  • Flight control problems (stiffness, limited movement) require gentle handling—avoid abrupt maneuvers and increase margins.
  • Flap failures typically mean higher landing speed and longer landing distance; plan a longer runway/landing area.
  • Landing gear issues (retractable aircraft) may require alternate extension procedures and possibly abnormal landing techniques. The correct actions are aircraft-specific—your POH is the authority.
Exam Focus
  • Typical question patterns:
    • Scenario diagnosis: “Symptoms suggest pitot-static issue—what do you cross-check and do next?”
    • “How do you manage an alternator failure to preserve essential equipment?”
    • “What changes in approach/landing do you expect with flaps inoperative?”
  • Common mistakes:
    • Assuming one instrument is correct without cross-checking.
    • Treating an electrical odor as “probably nothing.”
    • Forgetting that abnormal configurations often require more runway and a stabilized approach.

7.14.5 Describe emergency equipment and survival gear

Emergency equipment is onboard gear intended to prevent a minor problem from becoming fatal—especially if you must land off-airport or remain with the aircraft while waiting for rescue.

Signaling and locating
  • ELT (Emergency Locator Transmitter): designed to help search and rescue locate you after a crash/forced landing.
  • PLB (Personal Locator Beacon) (if carried): can supplement aircraft systems and stays with you if you must leave the aircraft.
  • Visual signaling: signal mirror, strobe, flares (where appropriate/legal), bright panels.

The key survival principle is: rescuers find you faster when you can transmit your location or create a strong visual signature.

Fire, first aid, and egress
  • Fire extinguisher: only helpful if accessible and you know how to use it quickly.
  • First aid kit: treat bleeding, exposure, and shock—common immediate threats after an off-airport landing.
  • Seatbelts/shoulder harnesses and a plan for evacuation: in water operations, egress planning is essential because disorientation is common after impact.
Environment-specific gear
  • Overwater: life vests (worn, not stowed), raft, thermal protection.
  • Cold/remote terrain: insulation layers, shelter, fire-starting tools, water purification.
  • Night operations: flashlight/headlamp with spare batteries.

A common misconception is that survival gear is “extra.” In many regions it’s the difference between discomfort and hypothermia.

Exam Focus
  • Typical question patterns:
    • “What equipment helps rescuers locate you, and how does it work operationally?”
    • Scenario: “You’re flying over cold water—what gear choices reduce risk?”
    • “Why should certain items be worn vs stowed?”
  • Common mistakes:
    • Stowing life vests where you can’t reach them after impact.
    • Carrying gear but not having it organized for quick access.
    • Neglecting environmental planning (temperature and remoteness) during preflight.

7.14.6 Describe engine failure during takeoff before VMC

In multiengine airplanes, VMC is the minimum speed at which you can maintain directional control with the critical engine inoperative and the other engine producing takeoff power (under a specific set of unfavorable conditions). An engine failure before VMC is especially dangerous because below that speed, you may not be able to keep the airplane going straight with one engine at high power.

Why “before VMC” changes the correct response

With asymmetric thrust, the operating engine yaws the airplane toward the dead engine. Rudder authority increases with airspeed. Below VMC, even full rudder may not counter the yaw—so trying to continue the takeoff can lead to a sudden loss of control.

Correct mindset: control first, then reject

If an engine fails on the takeoff roll or just as you’re becoming light but you are below VMC, the safest response is typically:

  • Reduce power (especially on the operating engine) as needed to regain directional control
  • Maintain centerline and stop/land straight ahead using remaining runway or suitable overrun

A key teaching point is that “more power” is not always safer in a twin. If you can’t control the yaw, adding power on the good engine can make the yaw worse.

Exam Focus
  • Typical question patterns:
    • “Why is engine failure below VMC so hazardous?”
    • Scenario: “Engine fails during takeoff roll—what is your immediate action and why?”
    • “Explain asymmetric thrust and rudder authority in simple terms.”
  • Common mistakes:
    • Trying to continue takeoff while below control speed.
    • Confusing climb performance with controllability (they are different problems).
    • Delaying power reduction on the good engine when directional control is being lost.

7.14.7 Assess engine failure after liftoff (AMEL, AMES)

For multiengine land (AMEL) and multiengine sea (AMES), an engine failure just after liftoff is a time-critical situation: you’re low, slow, and close to obstacles.

What you must accomplish quickly

Your first tasks are always:

  1. Maintain control (directional control with rudder; avoid aggressive bank angles)
  2. Pitch for the correct performance speed (typically the published single-engine climb speed, if available and appropriate)
  3. Configure for climb (reduce drag—gear up when positive climb is assured; flaps per procedure)

Only after you have the airplane under control do you move to engine identification and securing.

Identify–Verify–Feather (concept and why it works)

A widely taught structure is Identify–Verify–Feather:

  • Identify the failed engine (common cue: “dead foot, dead engine”—the foot not pushing is on the side of the failed engine because you’re pressing rudder toward the operating engine).
  • Verify by reducing power on the suspected engine—if the yaw gets worse, you picked the wrong one (so restore and reassess).
  • Feather (if applicable) to reduce drag from a windmilling propeller.

The verification step is what prevents a catastrophic error: shutting down the wrong engine.

Example scenario: failure at 200 feet AGL

You rotate, climb briefly, then you feel yaw and performance loss.

  • You immediately hold heading with rudder and set pitch to maintain safe airspeed.
  • You reduce drag (gear/flaps per procedure) and confirm positive climb or at least controlled flight.
  • If climb performance is inadequate, you may need to land straight ahead or within a shallow arc rather than forcing a climb that isn’t there.

A common mistake is trying to “save the climb” with excessive bank or pulling to hold altitude—both can lead to loss of control or stall.

Exam Focus
  • Typical question patterns:
    • “Walk through the first 5–10 seconds after an engine failure after liftoff.”
    • “Explain ‘dead foot, dead engine’ and the purpose of verify.”
    • Scenario: “You’re not climbing on one engine—what options do you consider?”
  • Common mistakes:
    • Skipping verify and securing the wrong engine.
    • Overbanking toward the operating engine (or letting the airplane roll away) instead of using small bank and proper rudder.
    • Fixating on checklists while airspeed decays.

7.14.8 Hypothesize approach and landing with an inoperative engine (AMEL, AMES)

An approach and landing with an inoperative engine is not just a normal approach with “less power.” It’s a high-workload situation with reduced go-around capability, increased asymmetry, and often higher required airspeeds and longer landing distances.

Planning: assume you may not be able to go around

In many light twins, a go-around on one engine is possible only if you are properly configured and at the right speed—and sometimes it is not practical at all (density altitude, weight, turbulence, runway environment). That means you plan to make the first approach stable and conservative:

  • Choose the longest, widest, least complex runway/water lane available.
  • Brief the approach early: configuration schedule, speeds per POH, and where you will commit to landing.
  • Minimize configuration changes late on final.
How asymmetric thrust changes your handling

With one engine inoperative, you typically need:

  • More rudder trim/pressure and a small bank toward the operating engine to maintain coordinated flight.
  • Careful power changes—adding power on the operating engine increases yaw and can destabilize the approach if you’re slow.
Example: stabilized single-engine final

A good single-engine final looks “boring”:

  • Airspeed steady (POH target)
  • Small corrections only
  • Centerline tracking with coordinated rudder/bank
  • Power changes gradual

A common error is carrying the approach too slow “to reduce landing distance,” then needing large power changes that push you toward VMC-related control issues.

Exam Focus
  • Typical question patterns:
    • Scenario: “Plan a single-engine approach—what runway and what approach style do you choose?”
    • “Why is the missed approach decision different with one engine inoperative?”
    • “What does a stabilized approach mean in this context?”
  • Common mistakes:
    • Treating it like a normal approach and delaying configuration decisions.
    • Flying too slow near the ground.
    • Making abrupt power changes with the operating engine.

7.14.9 Define multiengine operations

Multiengine operations are the knowledge and piloting skills unique to airplanes with two or more engines—especially the ability to manage asymmetric thrust and performance when one engine fails.

What makes multiengine different

In a single-engine airplane, engine failure primarily becomes a glide/landing problem. In a twin, engine failure becomes:

  • A control problem (yaw/roll due to asymmetric thrust)
  • A performance problem (reduced climb capability)
  • A systems problem (securing the engine, propeller control, fuel management)
Key terms you must understand conceptually
  • Critical engine: the engine whose failure most adversely affects performance/handling (often tied to propeller rotation direction and aerodynamic effects).
  • VMC: minimum control speed with one engine inoperative under specified conditions.
  • Single-engine best rate-of-climb speed (commonly published): the speed that usually provides the best climb performance with one engine inoperative.

The main misconception is thinking “two engines means twice the safety.” It can mean more options—if you maintain control and stay ahead of the aircraft.

Exam Focus
  • Typical question patterns:
    • “Compare engine failure handling in single vs multiengine airplanes.”
    • “Define VMC and explain why it’s a controllability limitation.”
    • “What is a critical engine, and why does it matter?”
  • Common mistakes:
    • Assuming multiengine failure response is mostly about performance, not control.
    • Confusing VMC with stall speed (they are different; either can occur first depending on conditions).
    • Forgetting that asymmetric thrust affects trim and workload continuously.

7.14.10 Describe maneuvering with one engine inoperative (AMEL, AMES)

Maneuvering with one engine inoperative (OEI) means performing climbs, level flight, and turns while maintaining control, coordination, and safe margins above both stall speed and VMC.

The coordination goal: minimize sideslip

In OEI flight you want coordinated flight (ball centered) with minimal drag. Many multiengine techniques use a small bank toward the operating engine to reduce rudder requirement and improve performance. The idea is to avoid “hanging on the rudder,” which creates drag and can reduce climb.

Turning considerations: why direction matters

When you turn, the aircraft’s yaw/roll coupling and asymmetric thrust can make one direction feel more stable than the other. As a general handling concept:

  • Turns toward the operating engine often feel easier to control because the bank can help oppose yaw.
  • Turns toward the inoperative engine can require more rudder and may degrade performance.

You still can—and sometimes must—turn either way; the key is to do it shallowly, at safe speed, and with coordinated control inputs.

Example: obstacle avoidance after engine failure

If you must alter course after an engine failure, you plan for:

  • Gentle bank angles
  • Maintaining the appropriate OEI airspeed
  • Avoiding “steepening the turn” when the nose drops (a common reaction that can increase stall speed)
Exam Focus
  • Typical question patterns:
    • “Explain why coordination matters more with one engine inoperative.”
    • Scenario: “You must turn back toward the airport on one engine—what are the risks and how do you manage them?”
    • “Why can excessive rudder be harmful (drag/performance)?”
  • Common mistakes:
    • Overbanking at low speed.
    • Flying uncoordinated because you’re focused on heading/altitude only.
    • Using abrupt power changes that create large yaw swings.

7.14.11 Demonstrate VMC operations

A VMC demonstration is a training maneuver that shows how directional control is lost as airspeed decreases with one engine producing high power and the other simulated inoperative. This is not a “see how far you can go” event—the entire point is to recognize the onset and recover immediately.

What VMC really represents

VMC is a minimum controllability speed, not a performance speed. Below it, full available rudder may be insufficient to keep the airplane from yawing/rolling toward the inoperative engine. Because the published VMC is determined under specific conditions, the actual controllability limit in your flight can be higher or lower depending on:

  • Weight (lighter weight can worsen VMC characteristics)
  • Center of gravity
  • Density altitude
  • Bank angle and configuration
  • Power on the operating engine
How a VMC demo is typically performed (conceptually)

Under instructor supervision and at a safe altitude, the setup usually involves:

  • Simulating one engine inoperative
  • Configuring the airplane in a takeoff-like state (as appropriate)
  • Gradually reducing airspeed while maintaining heading
  • Recognizing the first sign of loss of directional control (not waiting for a full departure)
  • Recovering by reducing power on the operating engine as needed, lowering the nose to regain airspeed, and returning to coordinated flight

The critical lesson: if you are near VMC and you add power on the operating engine, you may increase the yawing moment—so recovery often includes reducing power.

Exam Focus
  • Typical question patterns:
    • “Define VMC in operational terms and list factors that affect it.”
    • “Describe the purpose and safe recovery from a VMC demonstration.”
    • Scenario: “You’re slow on one engine and losing directional control—what do you do first?”
  • Common mistakes:
    • Treating the demo like a competition and allowing excessive yaw/roll.
    • Confusing VMC with stall onset and responding incorrectly.
    • Failing to prioritize airspeed recovery before trying to ‘muscle’ the airplane straight.

7.14.12 Describe navigation with one engine inoperative (solely by reference to instruments) during straight-and-level flight and turns (AMEL, AMES)

Navigating OEI solely by reference to instruments combines multiengine asymmetry with instrument-scan discipline. The challenge is that asymmetric thrust constantly tries to yaw/roll the aircraft—so if your scan is weak, small deviations build quickly.

Straight-and-level: what you’re really controlling

In OEI instrument flight, you’re continuously managing:

  • Heading/track (heading indicator, CDI/HSI, GPS track)
  • Bank and yaw (attitude indicator, turn coordinator, slip/skid indicator)
  • Altitude and performance (altimeter, vertical speed, airspeed)
  • Power and configuration (engine instruments on operating engine; secured engine status)

A practical technique is to trim aggressively: rudder trim (if installed) and a stable power setting reduce the need for constant pressure, freeing attention for navigation.

Turns on instruments: keep them shallow and deliberate

Instrument turns OEI should be planned and “paced”:

  • Use standard-rate or shallower turns as appropriate.
  • Roll in and roll out smoothly to avoid chasing the needles.
  • Monitor the slip/skid indicator—uncoordinated flight increases drag and can degrade climb/altitude hold.
Example: holding altitude while turning to an alternate

If you’re at a marginal altitude where climb is not possible, your goal may be “no worse than level.” During the turn, avoid letting the nose rise (airspeed decay) or the bank steepen (increased stall speed). If altitude begins to slip, it may be safer to accept a small descent while maintaining safe airspeed and control.

Exam Focus
  • Typical question patterns:
    • “What instruments are most important for OEI control in IMC?”
    • Scenario: “You must turn to intercept a course OEI—how do you keep it stable?”
    • “Why does trim matter more OEI?”
  • Common mistakes:
    • Fixating on navigation needles and neglecting bank/slip control.
    • Allowing slow flight during turns (airspeed bleed-off).
    • Making aggressive heading corrections that create oscillations and workload spikes.

7.14.13 Describe instrument approach and landing with an inoperative engine (solely by reference to instruments) (AMEL, AMES)

An OEI instrument approach adds two layers of risk: reduced aircraft capability and reduced outside visual cues. The goal is to create a stable, predictable profile early so you are not making large changes close to minimums.

Planning and briefing: build stability before you start down

Before starting the approach:

  • Choose the simplest suitable approach (precision or approach with the best guidance, when available and appropriate).
  • Brief: target airspeeds (per POH), configuration points, and how you will handle a missed approach.
  • Consider workload reducers: autopilot (if approved/working), approach mode, and early configuration.

A key point is being honest about performance: some aircraft/conditions may not support a missed approach OEI. That should shape your decision-making before you descend below a safe altitude.

Flying the approach: small changes, constant coordination

On OEI instruments, you want:

  • Power stability (avoid big throttle swings on the operating engine)
  • Configuration discipline (gear and flaps on a planned schedule)
  • Course/Glideslope tracking with gentle corrections
  • Coordination (ball centered as much as possible; trim to reduce pressure)

Because you have less excess power, you typically cannot “salvage” a low/slow approach by adding lots of thrust—adding power increases yaw and may destabilize the approach. That’s why the stabilized-approach concept is even more important OEI.

The missed approach decision

If the runway environment is not in sight at the required point, you must decide whether a missed approach is safe and feasible. This is not something you want to evaluate for the first time at minimums. You plan it in advance by considering:

  • Aircraft weight and density altitude
  • Expected climb capability OEI
  • Approach type and obstacle environment

If a missed approach is initiated, you must manage yaw aggressively and configure correctly—drag reduction (as appropriate) and maintaining safe OEI airspeed are essential.

Exam Focus
  • Typical question patterns:
    • “How does OEI change your instrument approach planning and briefing?”
    • Scenario: “You’re slightly low on glideslope OEI—what correction strategy is safest?”
    • “Discuss missed approach considerations OEI and why they must be planned early.”
  • Common mistakes:
    • Descending into a high-workload situation without a clear plan for missed approach feasibility.
    • Making large power changes that destabilize heading/track.
    • Continuing an unstable approach because “we’re already here.”