The hardest call in flying isn’t a maneuver — it’s the decision to fly at all. Here’s the framework: the legal floor, PAVE, IMSAFE, personal minimums, and a green/yellow/red process you can run before every flight.
Weather-related accidents — above all VFR flight into instrument conditions — are consistently among the deadliest in general aviation, and the chain almost never starts in the air. It starts on the ground, with a pilot who wanted to go, looked at a marginal picture, and found reasons it would probably work out.
The problem isn’t knowledge. It’s that an unstructured decision made under pressure bends toward the answer you want. The fix is a repeatable process: decide your limits calmly in advance, gather the same information every time, score it the same way every time, and let the process — not the pressure — make the call.
FAR 91.103 requires each pilot in command to become familiar with all available information concerning the flight before beginning it. For any flight not in the vicinity of the airport that explicitly includes weather reports and forecasts, fuel requirements, alternatives if the flight cannot be completed, and known traffic delays — and for every flight, runway lengths and the aircraft’s takeoff and landing distance data. Pilots remember the list as NWKRAFT:
Closed runways, unlit towers, TFRs, GPS outages.
METARs and TAFs for departure, en route, destination, and an out.
Ground stops, flow programs, expected routing.
At every airport of intended use.
Where you go if the flight cannot be completed as planned.
VFR legal minimum: destination + 30 min day / 45 min night at cruise (91.151). Treat an hour as your real floor.
From the POH, at today’s weight and density altitude — not the book’s sea-level standard day.
91.103 is the floor, not the decision. A flight can be perfectly legal and still be a bad idea for you, today, in this airplane. That’s what the rest of the framework is for.
The FAA’s PAVE checklist splits preflight risk into four buckets. Walk them in order, honestly, every time:
Health, rest, recency, and proficiency. Run IMSAFE (below). Legal currency is a floor — three landings in the last 90 days does not make you sharp in a gusty crosswind.
Airworthiness, inspections, squawks, fuel on board, and performance: weight & balance, density altitude, and takeoff/landing distance for the actual runways you will use.
Weather now and forecast (METARs, TAFs), winds and crosswind at every airport, terrain, airspace, NOTAMs, runway conditions, day vs. night.
Passengers with plans, a meeting, a rental return time, sunk cost of the drive to the airport. The most dangerous factor, because it distorts your read of the other three.
The “P” in PAVE gets its own checklist, because pilots are worst at evaluating themselves. Six questions, answered honestly:
Am I sick — even "just a cold"? Congestion plus altitude is a real problem.
Am I taking anything that affects alertness — or that the FAA prohibits?
Job, money, family — stress consumes the mental bandwidth flying needs.
8 hours bottle-to-throttle minimum and under 0.04 BAC (91.17) — and hangovers count.
Did I sleep? Fatigue impairs judgment before it impairs stick-and-rudder.
Am I angry, upset, or distracted? Strong emotion is a no-go item like any other.
Legal VFR minimums (91.155) tell you what’s lawful — 3 statute miles and cloud clearances in most airspace. They say nothing about what’s smart for your experience level. Personal minimums are your own numbers — ceiling, visibility, surface wind, crosswind, runway length, fuel reserve — written down when you’re calm, so the airport decision is comparison, not judgment.
| Factor | Legal VFR floor | Sample new-PPL minimum |
|---|---|---|
| Ceiling | 1,000 ft (for basic VFR) | 3,000 ft AGL |
| Visibility | 3 SM (most airspace) | 5 SM day · 7 SM night |
| Surface wind | No regulatory limit | 15 kt |
| Crosswind component | No regulatory limit | 7 kt |
| Fuel at landing | 30 min day / 45 min night (91.151) | 1 hour |
These are starting points, not gospel — the point is that you pick numbers above the legal floor and honor them. Raise them at night, at unfamiliar airports, or after a layoff; lower them gradually and deliberately as your experience grows, never in the moment because today’s flight needs it.
Put together, the process before every flight looks like this:
Standard briefing, METARs and TAFs for departure/en-route/destination/alternate, NOTAMs, and performance numbers (weight & balance, density altitude, takeoff and landing distance) for today’s conditions. Same sources, every time.
Rate each PAVE factor green (well inside your minimums), yellow (near a limit or degraded), or red (beyond a personal minimum or a legal requirement).
Any red: no-go — or change the plan until it isn’t red (different day, different route, different runway, an instructor in the right seat). Multiple yellows: treat the combination as red. All green: go.
Set en-route triggers before takeoff ("ceiling below 2,500 or visibility below 5 and I divert to X"). The go decision is never final — it renews at every checkpoint.
Well inside every minimum
Near a limit — mitigate, and never stack them
Beyond a minimum — no-go as planned
Watch the external pressures hardest. Passengers waiting, a rental return, three hours already spent driving and preflighting — none of it changes the weather. Decide what the flight would look like if nobody were watching and nothing were riding on it. A cancelled flight is a decision that worked.
FlightKit’s free Go/No-Go tool walks PAVE and IMSAFE against live METARs and TAFs for your route, checks the numbers against your personal minimums, and exports a PDF of the decision — so every flight starts with the same disciplined process.
The go/no-go decision is the deliberate judgment a pilot makes before every flight (and continuously during it) about whether the flight can be conducted safely. It weighs the pilot’s condition, the aircraft, the environment (especially weather), and external pressures against regulations and the pilot’s own personal minimums. A structured framework like PAVE makes the decision repeatable instead of a gut feel.
PAVE is an FAA risk-management checklist that divides preflight risk into four categories: Pilot (health, rest, currency, proficiency), Aircraft (airworthiness, equipment, performance), enVironment (weather, terrain, airspace, runways, day/night), and External pressures (schedules, passengers, and anything else pushing you to go). You assess each category honestly and decide whether the combined risk is acceptable.
IMSAFE is the self-assessment part of the "Pilot" in PAVE: Illness, Medication, Stress, Alcohol, Fatigue, and Emotion. If any item gets an honest "yes, that applies to me today," the flight deserves a hard look — most personal-minimums programs treat two or more as an automatic no-go.
Personal minimums are limits you set for yourself — ceiling, visibility, wind, crosswind, runway length, fuel reserve — that are more conservative than the legal minimums, chosen calmly on the ground rather than under pressure at the airport. They are not required by regulation, but the FAA strongly recommends them, and a written set is the single best defense against talking yourself into a marginal flight.
A common starting point for a new VFR pilot is: ceiling at least 3,000 ft AGL, visibility at least 5 statute miles, surface wind at or below 15 knots, and crosswind component at or below about 7 knots — tightening further at night or at unfamiliar airports. Those numbers are well above the legal VFR minimums on purpose. As your experience grows, you deliberately and gradually adjust them.
Get-there-itis (the FAA calls the broader pattern "plan continuation bias") is the tendency to continue toward the destination as planned even when conditions say stop. It is a factor in a large share of fatal weather accidents, especially VFR flight into instrument conditions. The counter is deciding your limits before the flight and treating a diversion or cancellation as a good outcome, not a failure.
No — it is continuous. The preflight decision gets you to the runway, but you should re-run it at every phase: before takeoff, at each checkpoint, and any time conditions change. Set hard triggers in advance ("if the ceiling drops below X or visibility below Y, I divert") so the en-route decision is already made before you are in it.
Short, practical guides on weather, planning, and staying current. No spam.