PA.VIII.F.ERR· Common Errors
Common errors
Common errors and how to fix them
VIII.F errors fall into three families: scan-breakdown errors (losing the scan during secondary tasks), comm-management errors (fumbling transmissions, missing read-backs), and automation errors (mismanaging the autopilot or GPS). The six below cover the common faults.
1. Heads-down on the secondary task
What it looks like: the pilot starts a GPS programming task, gets engaged in the menu structure, and 20 seconds later looks up to find the airplane 100 ft off altitude with 15° of heading drift.
Why: task fixation. The secondary task is structured and engaging; the scan is unstructured and feels boring by comparison.
Fix: break the secondary task into 3–5-second increments with scan returns. Half-finished GPS entries are fine; out-of-tolerance altitude is not.
2. Holding the radio button while flying drifts
What it looks like: the pilot delivers a long, careful radio transmission. Meanwhile, altitude is sliding.
Why: the transmission feels important; the scan is mentally backgrounded.
Fix: the scan continues during transmissions. Make the call short and scripted; eyes on the panel before, during, and after the transmission. If the call is going to take longer than 5 seconds, break it into chunks.
3. Missing ATC instructions
What it looks like: ATC issues a clearance ("Cessna 12345, turn right heading 270, descend and maintain 4,000"). The pilot reads back only the heading; the descent goes unacknowledged.
Why: cognitive overload — too much to process at once, or scan focus blocking comm processing.
Fix: write down or repeat back the full clearance. If unsure, ask ATC to "say again." The standard read-back format covers the assignment; if you can't read it back, you haven't heard it.
4. Mis-tuning navigation aids
What it looks like: the pilot intends to tune Approach on 124.5 but dials 142.5. No response from ATC; the pilot fumbles with the radio while flight tolerances drift.
Why: rushed input under hood pressure.
Fix: verify the frequency before committing. Read the active frequency aloud. Some installations include a comm test transmission ("Approach, Cessna 12345, radio check") to confirm.
5. Autopilot mis-engagement
What it looks like: the pilot engages the autopilot in HDG mode but the bug is on the wrong heading; the airplane begins turning unexpectedly. Or the pilot engages ALT hold while still in a climb, capturing the wrong altitude.
Why: not verifying the autopilot mode + reference values before engagement.
Fix: set the references first, then engage. HDG bug → engage HDG mode. Target altitude in the altitude preselect → engage ALT mode. Verify the mode display shows the intended state.
6. Manual override while autopilot is active
What it looks like: the pilot engages the autopilot, then makes a manual control input. The autopilot fights back; the airplane oscillates.
Why: instinctive correction when the autopilot's behavior doesn't match expectation — or the pilot didn't trust the autopilot in the first place.
Fix: either autopilot OR manual — pick one. If the autopilot is doing something unexpected, disengage it before applying manual inputs. Don't fight it.
How errors compound. Heads-down (#1) leads to flight tolerance bust. Missing ATC instructions (#3) leads to disorientation or wrong actions. Autopilot mis-engagement (#5) plus manual override (#6) creates cockpit confusion at exactly the wrong time. The discipline that prevents the chain: aviate first, prioritize the scan, execute secondary tasks in increments, verify before committing to automation. None of these are conceptually hard; all of them are workload-related, and all of them get harder under stress. The maneuver trains the habits before they're needed for real.
★ Next up
PA.IX.A.HOW · How to fly the maneuver
An emergency descent is the maneuver flown when rapid altitude loss is urgently required — in-flight fire, smoke or fumes in the cockpit, urgent medical issu…