Building a FRAT for Your Flight School: Go/No-Go Without the Guesswork

Almost every flight begins with a decision that carries more risk-management weight than anything that happens in the air: the go/no-go call. Should this flight happen, in these conditions, with this pilot, in this aircraft, today? Made well, it prevents the accident chain from ever starting. Made by gut feel — "it looks okay, let's go" — it is the point where subtle, accumulating risk factors slip through unexamined.

The trouble with gut feel is not that experienced pilots have bad instincts; it is that instinct is invisible, inconsistent, and impossible to teach. A student cannot learn a mentor's intuition. Two instructors can look at the same marginal morning and reach opposite conclusions with equal confidence. And even a good pilot's judgement degrades under the pressures — schedule, expectation, sunk cost — that are hardest to notice in the moment.

A Flight Risk Assessment Tool, or FRAT, exists to fix this. It converts the go/no-go decision from an opaque feeling into a structured, scored, repeatable process: a short checklist that scores individual risk factors, totals them, and turns the total into a clear signal — go, go-with-mitigation, or no-go. It does not replace judgement; it disciplines it, makes it consistent across everyone in the school, and — crucially for a training environment — makes good risk decision-making something you can actually teach. This is how you take the guesswork out of the most important call of the day.

A FRAT is a structured pre-flight checklist that assigns points to individual risk factors and sums them into a total that maps to an action. The mechanics are deliberately simple, because a tool that is complicated does not get used. The pilot answers a set of questions — each contributing points weighted by how much that factor raises risk — and the total lands in a band: a low score is a routine go, a middle score means go only after specific mitigations, and a high score is a no-go or requires escalation to a chief instructor or safety officer before the flight proceeds.

The power of scoring is that it catches the accumulation of risk that gut feel misses. No single factor on a marginal day is alarming on its own — a slightly tired pilot, a crosswind at the edge of comfort, a student's first solo cross-country, a bit of schedule pressure. Individually, each is easy to wave through. Summed on a FRAT, four moderate factors produce a score that says "stop and think," which is exactly the message the pilot needed and would not have generated on their own. The FRAT makes the invisible pile of small risks visible as a number.

The second benefit is consistency. When every pilot at the school uses the same FRAT, the go/no-go standard is the same whether the decision is being made by a 200-hour new instructor or a 5,000-hour veteran. That consistency is the foundation of a defensible safety process, and it is impossible to achieve with intuition alone.

Nearly every well-built FRAT is organised around the FAA's PAVE model, which sorts flight hazards into four categories so none of them is overlooked. Using PAVE as the skeleton of your FRAT ensures the tool covers the full risk picture rather than just the weather.

P — Pilot. Is the pilot fit and competent for this flight? Fatigue, recency and currency, experience in type and in the conditions, and physical and mental readiness all live here.

A — Aircraft. Is the aircraft suitable and airworthy for this flight? Maintenance status and open squawks, fuel, equipment for the conditions (day/night, VFR/IFR), and performance for the runway and density altitude.

V — enVironment. Weather, winds, ceilings and visibility, terrain, airspace, runway conditions, and daylight. This is the category pilots naturally weight most heavily — and a FRAT ensures it does not crowd out the other three.

E — External pressures. The most dangerous and most overlooked category: the pressures pushing a pilot toward "go" regardless of the other factors. Schedule pressure, a waiting passenger, a checkride booked, the cost of scrubbing, get-there-itis, the desire not to disappoint. Naming external pressure as a scored category is one of the FRAT's most valuable contributions, because it forces the pilot to acknowledge the very influence that most often pushes a marginal decision the wrong way.

Two established tools plug directly into the Pilot portion of a FRAT and make it sharper. The first is IMSAFE — the self-assessment mnemonic for fitness to fly: Illness, Medication, Stress, Alcohol, Fatigue, and Emotion. IMSAFE is the honest inventory a pilot takes of themselves, and it is the substance behind the FRAT's Pilot score. A FRAT question like "how many hours of sleep did you get" or "are you flying under any personal stress" is IMSAFE rendered as points.

The second, and arguably the most important habit a FRAT can reinforce, is personal minimums — the self-imposed operating limits a pilot sets that are deliberately more conservative than the regulatory floors and the aircraft's certified limits. The regulations define the legal edge of the envelope; personal minimums define where this pilot, at this experience level, chooses to operate well inside it. A FRAT is the natural place to encode personal minimums: the tool can flag when a flight is legal but outside the pilot's declared personal minimums for crosswind, ceiling, or visibility, turning an abstract commitment into an active check.

For a flight school, personal minimums are also a teaching device. A student who is taught from early on to set, write down, and respect personal minimums — and whose FRAT enforces them — internalises the single most protective habit in general aviation: the understanding that legal and safe are not the same thing, and that the sensible margin belongs to the pilot to define.

A FRAT should be tailored to your operation rather than copied blindly, because the risks that matter to a coastal Part 141 academy differ from those facing a mountain-based club. That said, a strong school FRAT shares common features.

Keep it short enough to be used every time — a form so long it gets skipped protects no one. Organise it by the four PAVE categories so coverage is complete. Weight the points so that genuinely serious factors (an inexperienced pilot in strong gusty crosswinds, say) can drive the score into no-go territory on their own, while a pile of minor factors accumulates into a "mitigate or reconsider" band. Define the action bands explicitly: what score is a clean go, what score requires specific mitigations and a note of what they are, and what score requires escalation to a chief instructor or a hard no-go. Tailor the factors to your fleet, your airport, your typical weather, and your student population — a FRAT for primary students should weight solo status and low experience heavily.

The escalation path matters as much as the scoring. The FRAT's real value in a school is that a middling score routes the decision to a second set of eyes — a chief instructor or safety officer — rather than leaving a junior pilot to talk themselves into a flight. That built-in check is where a lot of accident chains get broken, precisely because the person under pressure is not the only one deciding.

A FRAT filled out grudgingly and filed away changes nothing. Its value is realised only when it is embedded in a genuine safety process — which for a growing training organisation means a safety management system, the systematic, organisation-wide approach to managing safety risk through policy, risk assessment, assurance, and promotion. The FRAT is one of the SMS's most concrete instruments: it is risk assessment operationalised at the level of the individual flight.

Within an SMS, the FRAT does double duty. In the moment, it disciplines each go/no-go decision. Over time, the accumulated FRAT data becomes a safety-assurance goldmine: which risk factors recur, which flights are being flown at high scores, whether a particular time of year or type of operation clusters risk. That aggregate view lets the school manage risk proactively — adjusting policy, targeting training, tightening procedures — rather than only reacting to incidents after they happen. A pile of completed FRATs is a map of where your operation's risk actually lives.

The cultural piece is leadership treating the FRAT as protection rather than paperwork. When instructors see a high FRAT score respected — a flight scrubbed or mitigated without anyone being second-guessed for the cancellation — the tool earns trust and gets used honestly. When they see it overridden whenever it is inconvenient, it becomes theatre. The schools that get real safety value from a FRAT are the ones where a no-go is never the wrong answer, and where the person who scrubs is backed, not blamed.

The practical obstacle to any FRAT program is friction. A paper form at the dispatch desk that a rushing student skips, or a laminated card nobody fills in, delivers none of the benefit. The FRAT only works if completing it is a natural, low-effort part of the pre-flight routine — ideally built into the flow the pilot already goes through to get the aircraft.

This is where a FRAT integrates cleanly with a modern booking and dispatch process. If a student or renter already checks out an aircraft digitally, the FRAT can be part of that checkout: the flight is not dispatched until the risk assessment is completed, the score is captured with the booking, and a high score can automatically require instructor or safety-officer sign-off before the flight proceeds. That turns the FRAT from an easily-skipped extra step into an enforced gate that lives where the decision is already being made. A platform like Aviatize that handles scheduling and dispatch is the natural home for that check, and capturing every FRAT digitally is also what makes the aggregate safety-assurance analysis possible rather than a shoebox of paper forms.

Start simple. Build a short, PAVE-based FRAT tuned to your operation, tie it to personal minimums, define clear action bands with an escalation path, embed it in your dispatch routine so it is used every time, and treat a no-go as a good outcome. Do that and you replace the riskiest gut-feel decision in flying with a consistent, teachable, defensible process — which is exactly what go/no-go without the guesswork means.