Human-factors risk management

This element is the synthesis hub for Task H — the four risk-management strands that turn the aeromedical encyclopedia (K1), substances regulations (K2), and ADM frameworks (K3) into actual in-flight decisions. Hazardous attitudes (the patterns that produce bad calls), biases (the cognitive traps that miss information), situational awareness and disorientation (the failure modes of perception in flight), and self-assessment plus personal minimums (the structural commitments that hold under stress) — four strands, one element.

Detection without management is panic; management without detection is luck. The skill is the deliberate practice of both — and the structural commitments (personal minimums, framework discipline, the willingness to self-ground) that hold when stress would otherwise erode judgment FAA-H-8083-2.

hazardous attitudes

Five patterns produce most of the bad calls in general aviation. They are not personality flaws — they are situational responses pilots fall into under pressure, fatigue, or stress. AC 60-22 names them and pairs each with a one-line antidote. The point of memorizing them is to recognize them in yourself, in the moment, and apply the antidote consciously.

• Anti-authority — "Don't tell me what to do." Resentment of rules, procedures, supervisory feedback. Antidote: "Follow the rules. They are usually right."
• Impulsivity — "Do something quickly." Acting on the first idea without considering alternatives. Antidote: "Not so fast. Think first."
• Invulnerability — "It won't happen to me." Believing accidents happen to other pilots. Antidote: "It could happen to me."
• Macho — "I can do it." Taking unnecessary risks to prove capability. Most common in fatigue or after a series of successful pushes. Antidote: "Taking chances is foolish."
• Resignation — "What's the use?" Believing nothing the pilot does matters. Common after a mistake, an embarrassment, or a long stressful flight. Antidote: "I am not helpless. I can make a difference."

Pilots usually recognize these attitudes in others before themselves. The discipline is to apply the recognition inward — and to treat the antidote as a deliberate countermeasure to use, not a personality change to wait for. The frameworks taught in the ADM-frameworks element (K3) are where these get applied.

confirmation and expectation biases

Two cognitive failures show up consistently in accident reports. They are silent — neither one announces itself to the pilot — and they happen before the conscious decision they corrupt.

Confirmation bias is preferentially noticing information that supports a held belief while discounting information that contradicts it. The classic in-flight version: a pilot has decided the weather works for the trip; an updated METAR shows the destination ceiling dropping, but the pilot under-weights the ceiling and over-weights the still-acceptable visibility. The bias is not a lie the pilot tells themselves — it is a filter that runs before the data reaches conscious attention.

Expectation bias is hearing or seeing what you expect rather than what is actually there. The classic example: ATC clears the airplane to "taxi to and hold short" but the pilot expects "cleared for takeoff," reads back "cleared for takeoff," and rolls onto an active runway. Expectation bias is implicated in some of the most preventable runway-incursion and lost-comm events in the record.

Mitigations are deliberate practice, not "pay better attention." For confirmation bias: actively look for disconfirming information whenever you are committed to a plan; ask "what would make me cancel?" and check whether the answer is in front of you. For expectation bias: read back ATC instructions exactly as said and verify against the strip, chart, or expected sequence; treat any "I expected X" moment as a flag that X may not have been said. Biases interact with hazardous attitudes — invulnerability amplifies confirmation bias; impulsivity skips expectation-bias verification. Naming both layers is the first defense.

situational awareness, distractions, and disorientation

Situational awareness has three levels: perception (do I know where I am, what configuration the airplane is in, what it is doing?), comprehension (do I understand what those facts mean?), and projection (do I know what comes next, in 30 seconds, in 5 minutes?). Loss of SA is consistently among the top GA accident-cause categories — it is the single highest contributor in many year-over-year breakdowns.

Three types of disorientation pair with the three SA levels:

• Spatial disorientation — which way is up. The vestibular and visual systems disagree about attitude; common in IMC, at night, in turbulence. The aeromedical-factors element (K1) names the condition and the immediate correction (trust the instruments).
• Geographic disorientation — where am I. Lost or uncertain of position. Recovered with chart, GPS, ATC assistance, and a deliberate "I am here because…" reasoning step.
• Situational disorientation — what is happening. The airplane and the pilot are operating but the pilot has lost track of the larger picture. Recovered by reducing workload and rebuilding SA from the basics.

Distractions are the most common trigger for SA loss. The sterile cockpit principle — restrict conversation and activity to operationally essential items during taxi, takeoff, climb to cruise, descent, approach, and landing — was developed by airlines after CFIT accidents and is now standard GA practice. Brief passengers before flight that the cockpit goes quiet during those phases. The aviate-navigate-communicate sequence (canonically anchored in the Task G systems-risk element (G.R1)) is the recovery order when SA is degrading: fly the airplane, then navigate to a safe outcome, then talk to ATC. 14 CFR 91.3 gives the PIC authority to deviate from any rule to handle an emergency, and declaring or requesting priority handling is a tool, not a failure §91.3.

self-assessment and personal minimums

IMSAFE — the personal-readiness mnemonic — lives canonically in the ADM-frameworks element (K3); the application is here. Run IMSAFE before every flight; any "no" answer is a self-grounding signal; 14 CFR 61.53 makes the duty regulatory regardless of certificate status. The substances element (K2) carries the alcohol and medications detail that the M and A letters point to.

Personal minimums are the structural commitments that hold when in-flight pressure would otherwise erode judgment. They are numbers I write down before flight — above the regulatory and POH floor by a margin appropriate to my experience and currency. As an illustrative-not-prescriptive starting point, a new private pilot's day-VFR minimums might look like:

• Ceiling: 3,000 ft AGL day, 5,000 ft AGL night
• Visibility: 5 sm day, 7 sm night
• Crosswind: 12 kt (well below the airplane's demonstrated)
• Approach gates: stabilized by 500 ft AGL on final
• Last takeoff: 30 minutes before sunset (no night cross-country yet)
• Fuel on landing: 1 hour minimum (above POH reserve)
• Self-grounding triggers: any "no" on IMSAFE; any medication question not pre-cleared by AME

Those numbers tighten as experience and currency build and loosen only when the underlying experience does. The values above are illustrative — set your own with your CFI, your AME for the medical pieces, and your honest assessment of your current proficiency.

The bending-personal-minimums pattern is the failure mode this element exists to prevent. The scenario writes itself: in flight, weather along the route drops below your written ceiling, but you are 40 minutes from destination, the diversion adds an hour, passengers are tired, a hotel reservation is on the line, and the alternative is an awkward conversation. The temptation is to lower the minimum just for today. That is the pattern that produces the accident report. The antidote is the structural commitment — written down before flight, treated as a hard limit, with the diversion airport pre-briefed (named, fuel-state-budgeted) and the no-go decision pre-committed. The personal-minimums conversation does not happen in flight. This is the single most testable risk-management pattern in human factors, and the DPE will probe it in some form on virtually every checkride.

worked examples

Scenario 1 — bending minimums under passenger pressure.

Cruising VFR on a weekend trip, your written personal minimum for ceiling is 3,000 ft AGL day. METARs along the route are now reporting 2,500 broken with 2,000 ft scattered closer to destination. Destination is 40 minutes ahead. Your divert airport is 25 minutes back. Passengers are excited about lunch.

Walk the strands. Hazardous attitudes: macho ("I can fly this if I just stay below the layer") and impulsivity ("decide quickly and keep going") are the candidates. Biases: confirmation bias ("the visibility is still good, ceiling's not that low") is the silent failure. SA: perception is fine — I see the conditions — but projection (where will I be in 30 minutes?) shows the ceiling continuing to drop. Personal minimums: my written number is 3,000 ft; current is 2,500 and dropping. Decision: divert back to the pre-briefed alternate. Brief the passengers: "Weather is below my minimums; we are landing here and arranging ground transport." The personal-minimums conversation does not happen in flight. The skill is having pre-committed to that rule before launch.

Scenario 2 — readback mismatch on an instrument approach.

On a vectored ILS into a busy Class C, ATC clears you for a heading change to intercept the localizer. You read back, intercept, and start tracking. Two miles in, the airplane is shifting noticeably from the centerline and the localizer is tracking wrong. You realize the heading you read back is not the one ATC actually said.

Walk the strands. Expectation bias: the textbook example — you heard the heading you expected (the prior vector), not the one ATC said. SA: perception (the localizer movement) caught it; comprehension (the localizer is tracking wrong because the heading is wrong) closes the loop. Sequence: aviate first — keep the airplane stable on a known heading; navigate — request "say again" from ATC and rejoin the localizer; communicate — explicit verification of the new heading. Decision: stabilize on a safe heading, verify the clearance, intercept and re-establish. No declaration needed if the recovery is quick. The lesson the DPE wants is the bias name plus the recovery sequence — and the practice of reading back exactly what was said, not what you expected.