18.1 ADM, Hazardous Attitudes, PAVE, and DECIDE

ACS PA.I.H.K4 and PA.I.H.R2 sit on the knowledge test as judgment items, not personality quizzes. PHAK Chapter 2 and the Risk Management Handbook (FAA-H-8083-2) are the source text. Aeronautical decision-making (ADM) is a systematic approach to the mental process used to consistently determine the best course of action in response to a given set of circumstances. Stick-and-rudder skill keeps the airplane upright. ADM decides whether you should have launched, whether you keep going, and whether you divert. The accident chain is almost never one bad turn; it is a string of small “it will probably be fine” choices. Breaking any link — canceling, turning around, saying the antidote out loud — changes the ending.

Five hazardous attitudes and the PHAK antidotes

PHAK Figure 2-4 names five attitudes that wreck judgment and pairs each with a sentence you are supposed to say to yourself. Learn the antidote wording, not a paraphrase. The written test loves to swap them.

Anti-authority is not the same as macho. Skipping a run-up because “checklists are for students” is anti-authority. Launching into a 500-foot ceiling to show a passenger you can handle it is macho. Impulsivity is the go-around you never fly because you already started the flare. Invulnerability is “I’ve flown this scud a hundred times.” Resignation is sitting in a deteriorating cockpit and waiting for ATC or the instructor to save you. The antidote is a spoken reset, not a mood. If you cannot name the matching sentence, you do not own the attitude.

PAVE — four buckets before you start the engine

PHAK splits the risks of a flight into PAVE: Pilot, Aircraft, enVironment, External pressures. Run it in the planning room and again at the hold-short line.

• Pilot. Currency, proficiency, and fitness. This is where IMSAFE (Illness, Medication, Stress, Alcohol, Fatigue, Emotion in PHAK Chapter 2) lives. A legal third-class medical does not make a 14-hour duty day a good idea. Personal minimums belong here: ceiling, visibility, wind, crosswind, night, and runway length that are tighter than 91.155 / 61.57, written when nobody is waiting on the ramp.
• Aircraft. Airworthiness, fuel, performance for this density altitude and this runway, inoperative equipment under 91.213, database currency, and whether you actually know the avionics in that rental.
• enVironment. Weather, terrain, night, airports, airspace, icing, turbulence, and the destination that will be at night even if you launch in daylight.
• External pressures. Get-there-itis, a passenger’s dinner reservation, a borrowed airplane due back at dusk, the instructor waiting, the desire not to look timid. PHAK is blunt: external pressure is how a legal flight becomes an accident without a single regulation being broken.

A flight can be legal in every PAVE bucket and still be a no-go against your personal minimums. That is the point of writing them on the ground.

DECIDE when something changes

DECIDE (PHAK Figure 2-14) is the in-flight loop:

1. Detect that a change has occurred — or that an expected change did not.
2. Estimate the need to react. An open door at 1,500 feet in VMC is not an engine fire; do not treat them as the same clock.
3. Choose a desirable outcome (land now, divert, continue with a restriction).
4. Identify actions that produce that outcome.
5. Do the action.
6. Evaluate the effect, then loop. Acting changes the picture; the model is not a one-pass slogan.

An oil-pressure needle that drops may be a dying engine or a dead sender. Detect the indication, estimate how fast you must move (partial-panel weather versus a 50-foot pattern on a clear day), choose “nearest suitable airport” or “secure and land under you,” identify the AFM checklist items, do them, and evaluate whether pressure recovered or the engine is still making metal. Fixation on the gauge while the airplane descends into terrain is a DECIDE failure at Evaluate.

5P and 3P — still in the current handbooks

PHAK and the Risk Management Handbook still teach two more models. They are not antique oral-exam trivia.

5P is an SRM review: Plan, Plane, Pilot, Passengers, Programming. The Plan is weather, fuel, route, NOTAMs, and alternates. The Plane is mechanical status plus automation and databases. The Pilot is IMSAFE plus fatigue that will be worse at the destination than it is at the run-up pad. Passengers are a resource and a pressure source — brief them that a diversion is possible, then use them to look for traffic. Programming is the GPS and autopilot: set it on the ground or in level cruise, not in the flare. PHAK wants the 5P check at predictable points — preflight, before takeoff, about hourly or at mid-flight, before descent, and before the pattern — because those are the last cheap places to change the plan.

3P is the continuous loop: Perceive, Process, Perform. Perceive hazards with PAVE. Process them with CARE — Consequences, Alternatives, Reality, External factors. Perform controls with TEAM — Transfer, Eliminate, Accept, or Mitigate. “It will probably be okay” is a CARE failure at Reality. Waiting until morning eliminates the night-plus-fatigue hazard. Filing a closer alternate mitigates it. Transferring the risk might mean asking a more current instructor to make the trip, or not making it at all.

SRM versus CRM

Crew resource management (CRM) is the airline-born skill of using all available resources — people, hardware, and information — so a multi-person crew makes better decisions. Single-pilot resource management (SRM) is the same idea when you are the only required crewmember. You still have resources: the passenger who can hold a chart, ATC, Flight Service, the AFM, the checklist, the autopilot, and a 121.5 call. You do not have a copilot to catch the missed fuel totalizer. 5P is an SRM tool. CRM language on a PAR item about a solo 172 is the trap; the private-pilot airplane is an SRM problem that still uses CRM ideas.

Confirmation bias — ACS PA.I.H.R4

Confirmation bias is collecting the evidence that supports the decision you already like and discarding the rest. Expectation bias is hearing the clearance or the METAR you rehearsed. You wanted 1,500 overcast and you hear “five hundred” as “fifteen hundred.” You already decided to go, so the AIRMET for icing becomes “they always overlay that.” ACS puts this in Risk Management because it is how legal weather and a current airplane still produce a VFR-into-IMC accident. Countermeasures are mechanical: write the clearance after you hear all of it and read it back; compare the destination METAR to what you wanted; have a passenger listen; if you catch yourself saying “it will probably improve,” that sentence is the CARE Reality check you just failed.

Scenario: Jordan, the wedding, and “it won’t happen to me”

Jordan is a 90-hour private pilot with a passenger who needs to be at a lakeside wedding by 1700. Destination AWOS is 1,200 overcast and 3 miles in haze; his written personal minimums are 3,000 and 5. The airplane is legal. He tells himself he has flown worse, the bride is waiting, and “accidents happen to other people.” That is invulnerability plus external pressure. The PHAK antidote is it could happen to me, not a lower personal-minimums number invented on the ramp. PAVE already failed at Pilot (minimums) and External. DECIDE never starts because he never Detects that the plan changed — he only Detects the schedule. The ADM answer is to drive, delay, or cancel, then Evaluate that the wedding still happens and the airplane is still in one piece.