Guide · flight risk assessment
How to run
a preflight risk
assessment.
Five steps, the PAVE checklist done properly, and the part almost everyone skips: deciding your triggers before you are standing on the ramp with a passenger asking whether you are going.
The procedure
Five steps, in order.
- 01
Gather operational data
Collect METAR, TAF, SIGMETs, PIREPs, NOTAMs, aircraft performance data, pilot currency, and route information including terrain and alternates.
- 02
Apply the PAVE checklist
Evaluate Pilot (IMSAFE), Aircraft, enVironment and External pressures. Write down a specific risk in each category before engine start.
- 03
Set personal minimums triggers
Define hard go/no-go thresholds for ceiling, visibility, crosswind and fatigue. Triggers decided in advance are far easier to honour in flight.
- 04
Score route-specific hazards
Assess terrain exposure, historical accident density along your corridor, airport complexity, and en-route weather trends — not just the departure observation.
- 05
Document and decide
Record the assessment, state your decision and its rationale, and brief passengers or an instructor. Keep the record for training and review.
PAVE, properly
Four categories, and the one that actually kills people.
Pilot, Aircraft, enVironment, External pressures. Three of them are technical. The fourth is the reason accident narratives so often read as a sequence of individually reasonable choices.
03 · Triggers
Decide the no-go before you want to go.
A minimum you set at your desk is a number. A minimum you are negotiating with at 06:40, in front of a passenger, is a suggestion. Write the triggers down, in your own numbers, and treat crossing one as a decision already made.
FlightReady stores the first four and checks them against retrieved conditions on every assessment. The last two stay with you.
Paper versus computed
The same idea, with the data attached.
A paper FRAT asks the right questions. Its limitation is that it cannot see today's weather, does not know your currency, and forgets everything the moment you fold it.
| Paper or static form | FlightReady | |
|---|---|---|
| Who scores each line | You, by hand, on every flight | The engine, from retrieved data and your profile |
| Where the weights come from | Generic, printed on the form | Published base weights across 11 factors |
| Does it see today's weather | No — you transcribe it | Yes — retrieved at analyze time and stamped |
| Does it know your minimums | Only if you remember them | Stored, and checked line by line |
| Does it know the corridor's history | No | Historical NTSB records near the route, cited |
| What survives afterwards | A sheet of paper, if you keep it | A saved snapshot and your written rationale |
| Who decides | Pilot in command | Pilot in command — unchanged |
- WeatherAWC · on demand0.25
- Pilot readinessYour profile0.15
- Personal minimumsYour limits0.15
- Aircraft readinessYour aircraft0.12
- TerrainElevation model0.10
- AirportsFAA reference0.08
- Accident historyNTSB · historical0.08
- NOTAMsFAA · varies0.05
- Human factorsYour input0.05
- Weight & balanceWhen provided0.05
- TrafficCorridor context0.02
Relative weights · normalized at run time across available factors · missing data drops confidence
Questions
FRAT questions, answered.
Advisory only. FlightReady supports a decision, it never makes one. Verify critical information through official aviation sources. The pilot in command decides.
The form is not
the point. The pause is.
Whether you use paper or software, the value of a FRAT is that it stops you long enough to notice the factor you were about to accept without thinking.
Advisory only · the pilot in command decides