Cross-country flight planning risks

This element consolidates the risk-management side of cross-country planning: who you are, what airplane you're flying, what the environment looks like, what's pressuring you, and how each of those plays out in flight. PAVE is the framework; the decision is the point.

Three filters in order: regulatory minimums, personal minimums, PAVE. Pass all three with no external pressure driving the call → go. Otherwise modify (time, route, altitude, destination) or no-go. There is always a third option besides "press on or scrub": divert.

Personal minimums for cross-country

Pilot-imposed limits, set tighter than regulatory minimums. Cross-country minimums should be tighter than local-pattern minimums because the trip duration, distance, and unfamiliar conditions add risk.

Category	Local pattern	Routine XC	Mountain or unfamiliar
Ceiling AGL	1,500	3,000	4,000
Visibility SM	3	5	7
Surface wind	25	20	18
Crosswind	15	12	10
Convection within 20 NM	none	none	none
Forecast IFR along route	OK if local	none	none

Set them in writing before the flight, calibrated to the trip type, and don't adjust them under pressure. The point isn't the specific number — it's that you have a number and it's not the regulatory floor.

The pre-flight go/no-go

Three filters in order.

Regulatory minimums

The floor is set by regulation: currency for the pilot §61.23 §61.56 §61.57, fuel for the flight §91.151, weather for the airspace §91.155-class-c-d-e, and the broad preflight-information requirement §91.103.

There's no special regulatory currency for cross-country beyond the general PIC requirements. 61.93's cross-country endorsements apply to student pilots only.

Personal minimums sit above the regulatory floor (above).

PAVE risk assessment — four elements, each applied to the actual flight:

• P — Pilot. Current (61.56 flight review, 61.57 recency, 61.23 medical), proficient (recent cross-countries of similar distance/terrain/airspace/weather/aircraft — currency is the floor, proficiency is the actual standard), and IMSAFE for the full trip duration. IMSAFE: Illness, Medication, Stress, Alcohol §91.17, Fatigue, Eating/Emotion. A two-hour outbound + lunch + two-hour return is 5–6 hours of cockpit-and-airport time — assess for the whole thing, not just departure.
• A — Aircraft. Airworthy (Task B foundation), equipped for the conditions (icing, IFR, night), performing for the projected density altitude, fuel for the trip + 91.151 reserve + personal pad. Inop equipment runs through the 91.213(d) RAKETS flow if applicable (Task B R1).
• V — enVironment. Weather along the whole route (Task C territory — current, forecast, hazards, synoptic), terrain and airspace per K1 and K2, fuel availability at planned stops.
• E — External pressures. Schedule, paying passengers, sunk cost, ego, "I told everyone I'd be there." Name them out loud during PAVE — speaking pressures aloud reduces their power. If external pressure is the only reason "yes" is winning, that's a no-go signal.

Decide. Pass all three filters AND no external pressure is driving the call → go. Any filter fails or pressure is the deciding factor → modify (different time, route, altitude, destination) or no-go. If you'd be uncomfortable explaining the decision later, don't make it.

Continuing or diverting in flight

The flight doesn't end at "go." Every decision point en route is a re-evaluation.

Divert triggers

• Ceilings or visibility deteriorating below personal minimums and trending worse
• Fuel projected below VFR reserve at destination
• PIREPs ahead worse than forecast
• Convective activity over or near route or destination
• Any IMSAFE-readiness element degrading inflight (fatigue spike, ill feeling)
• Equipment failure that reduces capability for the remaining flight

Pre-flight prep that makes the call easier

• Identify divert candidates BEFORE departure — at least two per leg
• Pull their METAR/TAF/fuel/runways during preflight
• Write divert criteria on the kneeboard — "if KXYZ < 1,500 BKN or vis < 5 SM, divert to KABC"
• Mechanical execution when the trigger fires

ATC limits — what flight following will and won't do

ATC can provide traffic advisories, painted-weather vectors when workload permits, and emergency assistance. ATC does NOT provide IFR-style separation for VFR, vector you through clouds, or make weather decisions on your behalf — those stay with you (AIM 4-1-15). Service is workload-based; ATC can decline at the initial request or terminate later. "Remain VFR" is a conditional — refuse the instruction if compliance would compromise VFR (see K1 for the request/refusal mechanics).

EFB failure mode awareness

EFBs fail. Common modes: iPad overheating (summer cockpit, direct sun, ambient 90°F+), battery drain, software crash, dropped device. Pre-flight habits that pay off: paper sectional or PDF backup in the airplane, backup device or external battery, headings and times in the nav log written down. EFB-off contingency is a five-step recovery: acknowledge → fly first → switch to backup → continue with pilotage/DR/VOR → communicate to ATC if relevant. The DPE will pull the EFB mid-flight; rehearse the recovery before the practical.

Plan-continuation bias and external pressures

Plan continuation bias — pushing toward the destination despite mounting evidence the conditions don't support it. The most reliable contributor to GA fatal accidents. The pattern is incremental: each step of degradation looks survivable individually; the trend is what should be the warning.

The return leg compounds three factors. Fatigue (you've already done one cross-country plus whatever happened at the destination). Schedule pressure peaks (work tomorrow, expensive overnight if you scrub). Weather may differ (morning departure vs. afternoon return is a different forecast). The accident pattern: pilot leaves comfortable in the morning, completes the destination, faces deteriorating return weather, and continues because almost home. Recognize the return leg as the highest-pressure decision of the day, not the easiest.

Three protections against external pressure

• Name pressures out loud during PAVE preflight. "I have a meeting tomorrow but the weather doesn't care about my meeting." Speaking pressures aloud reduces their power.
• Pre-set decision points in writing. "If KXYZ ceiling 5,000 by my arrival, fly the route. If 3,000 or below, divert." Then act mechanically when the trigger fires.
• Treat divert as the default option, not as defeat. The three real options are land short, divert, scrub. Pressing on isn't on the safe-options list when the trend is bad.

Worked example:

• Marginal-VMC departure that becomes a divert mid-flight. Preflight: departure conditions 4,500 BKN at 6 SM (within personal mins of 3,000 / 5). Destination KPRC TAF: 1,800 BKN at 4 SM by arrival — below personal mins. The pilot launches anyway, pressured by a paid passenger on a return flight. En route, the destination ATIS reports 1,200 BKN at 3 SM — well below personal mins. Two divert candidates were identified preflight: KSEZ (25 NM SE, current METAR 5,000 BKN at 7 SM, within personal mins) and KFLG (35 NM N, marginal). Decision: divert to KSEZ mechanically — the trigger was the destination ATIS reading below the pre-set criterion. The pilot announces intentions to ATC, breaks off the approach to KPRC, lands at KSEZ. Cost: 30 minutes of extra flight time, an unhappy passenger, a $40 fuel stop, and an apologetic phone call. Compared to the alternative — pressing on into 1,200 BKN at 3 SM, then either VFR-into-IMC or arriving at the runway in unflyable conditions — the divert is unambiguously the right call. The reason it worked: the criterion was pre-set on the kneeboard, the divert candidates were pre-pulled, and the execution was mechanical when the trigger fired. Without that preflight prep, the in-flight call becomes negotiated against the passenger's frustration — and get-there-itis wins.