This article answers common questions about Safety Hub. It is for pilots, instructors, safety officers, and anyone else using Safety Hub day-to-day.

Why you see a blank page or "no access" message

Safety Hub access requires your FSP role must include the Access Safety Hub permission (canAccessSafetyHub). Without it, you cannot sign in to SMS at all.

This permission isn't automatic — an FSP administrator grants it through Settings → Users → Roles & Permissions → Edit Role → Permissions in the FSP shell. If you cannot reach Safety Hub, ask your administrator to check the Safety Hub section of your role.

See the "Safety Hub permissions overview" article for the full permission list and suggested role bundles.

This is a visibility issue, not a permission issue.

Safety Hub (SMS) uses two independent axes:

If you have the Manage Safety Reports permission but a report is not visible to you, you are probably not a member of the Safety Team the report was routed to. Ask a Safety Manager to add you to the correct team in Settings → Safety Team.

The only exceptions are the Accountable Executive and Safety Managers — they have a read-only bypass that lets them see every record across the organization regardless of team membership.

Note: Even canManageSafetyHubSettings does not grant cross-team visibility. You still need to be on the team — or be designated a Safety Manager — to see records assigned to it.

If someone does not appear in an Accountable Executive, Safety Manager, or team-member picker, they have not been flagged as a Safety Officer on their FSP user record.

An FSP administrator must enable the Safety Officer flag on the person's FSP profile. Safety Hub refreshes the picker list from FSP every time you open it. Removing the flag in FSP automatically removes the person from all Safety Hub slots.

See the "Configure your Safety Team" article for the full setup steps.

FRAT and Weight & Balance records on a reservation are time- and role-gated. You can edit them only within approximately one hour of the scheduled event, and only if you are assigned to the reservation.

If the reservation is in the future and you are not assigned to it, the FRAT item will not appear in the web Preflight checklist. This is expected behavior.

The full FRAT execution flow — including the high-risk threshold and flight-authorization gate — runs in the Pilotbase mobile app (Preflight suite), not in the web Safety Hub. The web Safety Hub shows the management and record layer: the Risk Assessments list, FRAT detail (read-only after submission), and the Weight and Balance register.

If you need to complete a FRAT, open the reservation in the Pilotbase mobile app before your flight.

The AI-generated Conditions Summary needs a departure airport to fetch live METAR, TAF, AIRMET, and SIGMET data. Enter the departure airport in the assessment form first, then the Conditions Summary will generate. You can also use Refresh Conditions Summary to update it after adding or changing the departure.

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

Reports auto-route to the Safety Team for the location associated with the report. If the correct team does not appear as the assigned team:

Public Safety Report submissions generate a Report ID (format: RPT-YYYYMMDD-XXXXXX) shown at the time of submission. There is no email confirmation — the reporter must save the Report ID at that point.

To check the status of a submitted report, use the Check Report Status link from your organization's public Safety Hub page and enter the Report ID. The status page also shows your safety team's contact email (set as the Safety Team Inbox) if you need to reach them. Status progresses from Submitted through review to Closed as the safety team works the report.

If you cannot find your Report ID, contact your organization's safety team directly.