A Flight Risk Assessment Tool (FRAT) assessment lets you score the risk of an upcoming flight before you fly. This article walks you through opening, completing, and submitting an assessment in Safety Hub — including reading your score, applying mitigations, and understanding what happens after you submit.

Note: FRAT execution — filling out the form, scoring risk, and getting go/no-go authorization — runs in the Pilotbase mobile app (Preflight). The web Safety Hub is the management and record layer: it shows all submitted assessments, lets you start a new one, and stores completed records. This article covers the web flow. For the mobile Preflight experience, see the "Safety Hub for pilots" article.

Each assessment uses a form configured by your safety team. The built-in form templates are FAA Default FRAT and IMSAFE Checklist, and your school can set up custom forms of its own. (The FAA Default template is organized around the PAVE structure — Pilot, Aircraft, enVironment, External pressures.) The form presents a set of questions; each answer carries a risk value. Safety Hub adds those values together to produce a total score and assigns a risk level (for example, Low / Medium / High) based on thresholds your admin has set.

The assessment also includes: - Available Mitigations — actions you can apply to reduce your final score. - Risk Summary — shows Initial risk (before mitigations), Mitigation reduction, and Final risk. - Conditions Summary — an AI-generated weather and advisory analysis for your departure airport (METAR, active AIRMETs, convective advisories). This requires a departure airport to be entered.

The Conditions Summary is generated by AI. Always cross-check against official sources before flight.

In the Safety Hub left sidebar, select Risk Assessments under the PREFLIGHT group.

The list shows all assessments across your organization. Use the All Statuses and All Risk Levels filters to narrow the view.

A few things to know about the list:

Work through each question in the Risk Assessment Questions section. For each item, select the answer that best describes your current situation. Safety Hub totals the risk values automatically as you go, and a progress bar tracks how many questions you've answered.

The Linked Source panel shows the reservation the assessment is tied to (aircraft, schedule, and crew). The header shows the assessment status and its current risk chip, and names the threshold configuration the score is measured against.

To generate a Conditions Summary, enter your departure airport in the designated field. Safety Hub fetches live METAR data, active AIRMETs, convective advisories (with Zulu validity windows), and a plain-language recommendation.

If you skip the departure airport, you'll see: "Enter a departure airport to generate a Conditions Summary."

After you answer the questions, the Risk Summary panel shows three numbers:

The Threshold Ranges listed under the summary (for example, Low ≤0 / Medium 1–6 / High ≥7) are set by your safety admin. Your final score falls into one of these ranges, and Safety Hub labels it accordingly. The resulting level and score appear together as a chip — for example, Low (0).

If your Initial score is higher than you'd like, scroll to Available Mitigations. Select one or more mitigations from the list. Each mitigation carries a point value; Safety Hub subtracts those points from your Initial score and updates the Final score in the Risk Summary.

Apply mitigations that genuinely describe actions you will take — the record is auditable.

When you're satisfied with the form and mitigations, select Submit at the bottom of the assessment.

After submission: - The assessment status changes to Complete in the list. - High-risk assessments may be flagged for instructor review. The go/no-go authorization gate runs in the Pilotbase mobile Preflight flow; the web record reflects the outcome. - You can select Create Safety Report from the assessment detail to escalate a high-risk finding into the SMS Safety Report workflow.

Select any row in the Risk Assessments list to open its detail. Safety team members (with the Configure FRAT permission) can also use the Edit assessment inline action, and for them a submitted (Complete) assessment is not locked in the web app — they can reopen and edit it. When they do, Safety Hub asks them to confirm with a Reopen submitted assessment? prompt, and confirming flips the assessment back to In Progress so it can be changed and submitted again. Users without Configure FRAT see a Complete assessment as a read-only summary.

If you're on your safety team, an Audit Trail panel appears inline on the assessment detail with a timestamped history of every change. This panel is only shown to Safety-Team users.

"Enter a departure airport to generate a Conditions Summary" appears. Add your departure airport to the assessment before requesting AI weather analysis. The field is in the assessment form, not a separate settings page.

The form I need isn't in the Select Assessment Form list. Your admin controls which forms are published. Contact your safety manager, or see the "Configure FRAT templates" article.

I can't see any assessments in the list. You need the Access Safety Hub permission in FSP. Ask your FSP administrator to confirm your role includes this permission. The list is operator-wide — once you have access, you see every assessment across your organization, not just those tied to a particular team.

The assessment appears but has no editable fields. If you have the Configure FRAT permission, you can reopen a Complete assessment for editing in the web Safety Hub (see "Check an existing assessment" above); without it, a Complete assessment opens as a read-only summary. The roughly one-hour edit window near the reservation applies to the Pilotbase mobile app (Preflight) flow, not the web app — if you're completing an assessment on the reservation or on mobile, finish it before that window closes. If a web field still won't let you edit, confirm you have the right permission and that the assessment isn't open elsewhere.