Operations8 min read

Flight Risk Assessment Tools for Flight Schools: How Dispatch Kills the Marginal Flight Before Preflight

How flight schools build a Flight Risk Assessment Tool into the dispatch decision, why the green/yellow/red score belongs on the booking screen before preflight, and how a written FRAT policy keeps CFI judgment consistent across the staff on a marginal Saturday morning.

A dispatcher on a Saturday morning has three lessons booked before 1100. Ceilings are 1,800 broken, three miles in mist, forecast to lift by 1000. The 0800 dual is a 3,000-hour CFII on a commercial student. The 0900 slot is a private-pilot student on their fourth dual, going out with a newer CFI. The 1000 slot is a solo cross-country by a student who first soloed in April. All three flights are legal under the school's minimums. Two of them should not leave the ramp. The dispatcher has no written tool to distinguish which two, and the chief instructor is at the field on the other side of the sectional. The 0900 flight departs because the CFI thinks it is fine. The solo cross-country departs because the student called ready. By 1030 the CFI has cancelled back to the pattern. The solo student is on the ground at a diversion field forty miles out. Nobody flew into weather they were not legal for. Two of the three flights just should not have flown.

That is what a flight risk assessment tool is for. It is not a weather minimums SOP, it is not a currency check, and it is not a checklist the student runs in the airplane. It is a numerical score the dispatcher and the CFI compute against the specific booking, and it is the number the school pins its go-no-go call to on a marginal day.

What a FRAT Actually Does

The FAA's Flight Risk Assessment Tool is a scoring worksheet that assigns numerical values to pilot, aircraft, environment, and mission factors and produces a green, yellow, or red risk category before the flight departs. The default VFR template scores twenty conditions and the IFR template scores twenty-two. Each condition that applies to the planned flight adds to the total. Green is a routine flight the school releases without special handling. Yellow is a flight that needs a documented mitigation before it dispatches. Red is a flight the school does not release. That last line is what a legal-minimum SOP does not enforce, and what a FRAT does.

The regulation floor is a different question. The school's weather minimums SOP sets the ceiling and visibility a lesson has to meet. The regulation says nothing about whether a 12-hour-total-time student should be dispatched into a marginal ceiling on a solo cross-country. The dispatch decision has to. The FRAT gives that decision a structure the front desk can defend without asking the chief instructor every time.

Why the Legal Answer and the Dispatch Answer Are Different

The pattern shows up in every safety-related SOP a flight school writes. The same shape runs through the density altitude and VFR fuel reserves posts. The legal minimum is the floor. It is not the dispatch number. A flight that meets 91.155 with a low-time student, an aircraft carrying an open deferred squawk at the margin, a forecast trending down, and a CFI who has been on since 0600 is a flight that should not be released even though nothing in the FARs prevents it.

A FRAT collapses those factors into a single number the dispatcher, the CFI, and the student can all read the same way. Ceiling at forecast reported delta, pilot total time, time in make and model, hours flown in the last 24, crosswind component versus the airplane's demonstrated number, aircraft airworthiness status, night-versus-day, terrain, distance from home field. Each factor gets a value. The total scores against a threshold the chief instructor set. Green goes. Yellow gets a call. Red does not fly.

The Factors That Actually Predict Trouble

The FAA's default FRAT template is a starting point. A school running one against its own accident and incident data gets closer to what actually predicts trouble at that school. The pilot side almost always dominates. Total time under 100 hours, time in make and model under 10, currency in category expired inside the last 90 days, and any solo lesson flown without the primary CFI on the field are all correlated with the incidents that show up in the training file the following month.

Weather comes second. Ceiling within 500 feet of the school's minimum, visibility within two miles of the school's minimum, and thunderstorm activity within 50 nautical miles are the leading environmental factors. The aircraft side is smaller in most primary training operations, but any open squawk affecting a system the student is likely to use, a recent 91.213 deferral, or an oil consumption trend outside the airplane's baseline all belong on the sheet.

The operational side is the one schools most often miss. A 0700 primary lesson on the first hot Saturday of July has a different risk profile than the same lesson at 1500. A CFI on their fourth flight of the day is not the same risk as the same CFI on their first. Neither factor shows up in the airman certification standards. Both belong on the FRAT.

Where the FRAT Belongs in the Booking

A FRAT scored on a paper form at the dispatch desk is a paper form. The dispatcher fills it in, files it, and the next flight starts from zero. The value shows up over time when the score is captured against the booking, retained, and queryable. A scheduling platform that already knows the pilot, the aircraft, the route, the forecast, and the CFI on the block can compute most of the FRAT automatically and surface the yellow-or-red threshold before the booking is confirmed. The dispatcher does not have to remember to run the check. The system runs it and the human decides.

That is the same discipline that runs through the weather minimums SOP and the fuel policy. HangarOS carries the FRAT score on the booking record for exactly that reason, and the audit trail is what makes the score defensible when the chief instructor pulls the week's flights on Monday.

The Threshold Is a Chief Instructor Decision

The FAA template scores against a matrix the FAA published. A flight school running the FRAT internally sets its own thresholds against its own risk tolerance. A conservative school will treat a yellow score as a chief instructor consult before dispatch. A more aggressive school will treat yellow as a mitigation the CFI documents on the release. Neither answer is wrong on its face. Both are the chief instructor's call, in writing, applied uniformly across the CFI staff.

The trap schools fall into is the one where the threshold moves with the day. On a slow Tuesday, a yellow score cancels the flight. On a full Saturday with revenue on the line, the same score becomes a green. The dispatcher sees this. The CFIs learn it. Six months later the FRAT is decorative and the board has drifted back to the CFI's feel, which was the state the FRAT was written to replace. The FAA's introduction to safety risk management is worth handing to every new hire, because the SRM discipline behind the FRAT is what keeps the threshold honest through a busy weekend.

Audit the Overrides

The audit trail on a FRAT is not the flights that scored green and departed uneventfully. It is the yellow flights that departed with a mitigation and the red flights that got rewritten as yellow. A chief instructor pulling the retained scores weekly finds the two patterns that matter. The first is a CFI who scores every marginal flight as yellow and then overrides it. The second is a dispatcher who scores every red flight as yellow before showing it to the CFI. Neither pattern surfaces in the incident report, because there was no incident. Both surface in the audit.

If two CFIs at the school score the same flight two grades apart, the score is not calibrated. The chief instructor projects the previous week's borderline bookings on the whiteboard at the next standardization meeting, walks the staff through the score, and the number the school uses drifts back toward the standard the chief instructor set at the start of the season.

The Point Is the Cancellation That Never Made the Log

A FRAT that never cancels a flight is a FRAT that is not working. The value is in the flights that scored yellow, got a mitigation, and flew safely, and the flights that scored red and did not fly at all. Neither shows up in an accident summary, because there was no accident. The schools whose incident rate stays flat as the fleet grows are not the ones with better airplanes. They are the ones whose dispatch score board catches the marginal flight on Friday afternoon, when the fix is cheap.