Common errors

Emergency approach and landing errors are the highest-stakes errors in the PPL curriculum — many of them are the chain links between an engine failure and an NTSB report. The eight below cover the common faults; the safety-critical ones (#1, #2, #4) are explicitly the kill-chain scenarios this task is built to prevent.

1. Stretching the glide (the central misframing)

What it looks like: the pilot is slightly short of the chosen field. They pull up to "stretch" the glide. Airspeed bleeds below V_BG; the airplane sinks faster; the field gets further away. In the worst case, the airplane stalls before reaching the field.

Why: the instinct to "pull up to stretch" the airplane's reach. It works on intuition (pull up to go further); it fails on aerodynamics (slow + nose-up = back side of power curve + reduced glide range).

Fix: hold V_BG. If you can't make the chosen field at V_BG, pick a closer field or commit to landing short of the chosen field. Stretching the glide is the misframing that kills pilots; the correct response is acknowledging the math.

2. Fixated on restart, forgot to fly

What it looks like: the engine fails. The pilot's eyes lock on the panel, running through restart items. Meanwhile, the airplane has descended 800 ft below the altitude where the field was reachable. The pilot looks up; the field is no longer in glide.

Why: troubleshooting instinct overriding flying priority. The brain wants to "fix the problem" — but the airplane is still flying / gliding, and fixing requires altitude that's being spent.

Fix: fly first, troubleshoot second. Pitch for V_BG, identify a field, then start the restart sequence. If the restart fails, the airplane is already pointed at a landing area; if the restart works, you've lost only 30 seconds of altitude.

3. Picking the field too late

What it looks like: the pilot stays in the troubleshoot loop or scans uncertainly for "the best field" until they're below pattern altitude. By then, options have shrunk dramatically.

Why: indecision. The pilot wants to find "the right" field rather than "a sufficient" field.

Fix: decide within 30 seconds. A sufficient field chosen at 2,500 ft AGL is much better than a perfect field chosen at 500 ft AGL. The decision is timely first, optimized second.

4. Trying to make the airport when an off-airport field was reachable

What it looks like: the pilot points at the nearest airport, which is 6 nm away at 2,500 ft AGL. Glide ratio gives 5–6 nm of range. The pilot tries to stretch (#1) and either stalls or lands short of the airport's runway — possibly in obstacles.

Why: preference for "the proper place to land" overriding what's actually reachable. Cultural — pilots want to land on runways.

Fix: closer is better than longer. An off-airport field 2 nm away is more reachable than a runway 6 nm away. The DPE evaluates whether the chosen field was the best available, not the "most airport-like."

5. Configuring too early

What it looks like: the pilot adds full flaps on downwind because "this is a landing." The airplane loses altitude rapidly to drag; the chosen field becomes harder to reach; on short final, the pilot is short.

Why: habit from normal landings (B, D, F). Treating engine-out as a normal landing with the throttle off.

Fix: configure when assured of reaching the field. First notch on base. Full flaps on short final only. Gear (if applicable) when the field is committed.

6. Forgetting to communicate

What it looks like: the pilot flies the maneuver competently but never declares or squawks. ATC has no idea anything is wrong; if the landing goes badly, no search-and-rescue response is initiated.

Why: task saturation — comm drops first.

Fix: brief the comm call before the maneuver during training. Have the radio call ready: "Mayday, Mayday, Mayday, Cessna 12345, engine failure, attempting forced landing near [position]." Make the call after the field is selected but before short final.

7. Not briefing passengers

What it looks like: the pilot completes the procedure but doesn't tell the passengers what to expect. Passengers panic or interfere with control inputs.

Why: focus on the airplane and the field; passengers feel like a distraction.

Fix: briefing is part of the procedure. After the field is selected, brief: "We're going to land in that field. Tighten your seatbelts. Door unlocked before touchdown. Brace position when I call brace."

8. Wrong checklist (e.g., engine fire instead of engine-out)

What it looks like: the pilot reaches for the emergency checklist and runs the wrong one. The actions don't match the actual emergency; the airplane's state worsens.

Why: stress + memory + similar-looking checklist labels.

Fix: identify the emergency before reaching for the checklist. Engine quiet + no power + airplane gliding → engine-out checklist. Engine running with smoke → fire checklist. Different problems, different procedures.

How errors compound. Fixation on restart (#2) consumes altitude that's needed for field selection (#3). Late field selection (#3) leaves only distant options, tempting the airport-attempt (#4). The airport attempt produces the stretching trap (#1), and the chain may end in a stall-spin from low altitude. The discipline that prevents this whole chain: fly first, decide early, commit to the achievable. Each step is independent; getting any one of them right makes the next more likely to go right. Practice the sequence in simulated emergencies so it's available in the real one — when the consequences are not academic.