Flying Rhino
RHINO AVIATION

Preflight Planning

Admin Home

  • Admins can change their own password, stored weight, default aircraft, color theme, and output date format from the Admin home page.
  • The Preferences card stores your weight, default aircraft, separate single-leg and multi-leg favorite form templates, VFR and IFR personal flight minima, theme, and output date format.
  • VFR and IFR Personal Mins are independent and optional. Each set may contain any combination of minimum ceiling, minimum visibility, maximum wind speed, maximum crosswind component, and maximum gust factor.
  • On the Flight page, the selected VFR or IFR flight type determines which minima set applies. An available weather value is shown in red only when it is beyond a configured limit in that set. If that set is entirely blank, no personal-minimum coloring is applied.
  • The most recently generated template for the same route mode in this browser takes precedence while it remains available. Otherwise, form generation uses the single-leg or multi-leg favorite, then the first available template.
  • If either favorite template is deleted, disabled, or no longer visible to you, the Dashboard identifies the affected route mode and links back to Preferences.
  • The theme chooser previews immediately. Save Config stores the selected theme and output date format as per-user preferences.
  • The subpage buttons at the top lead to Users, Roles, Fuels, Notices, Config, NAS Data for users with reference-data permission, and root-only Failed Logins.

NAS Data

  • Admin > NAS Data manages staged airport, runway, frequency, DCS, and timezone reference data.
  • Update Reference Data runs in the background. Conditional update stops when no source is newer and reports that no changes were needed; Full rebuild stages all sources using normal download caches; Forced complete rebuild bypasses those caches and also rebuilds airport timezone assignments. Only one reference-data operation may run at a time; a second request identifies the user who started the active NAS data update.
  • Rebuild airport timezones may be added to a conditional or full rebuild. In conditional mode it applies when newer source data causes staging to run. A forced complete rebuild always includes it. Select Download preview/next-cycle data to request preview data from sources that provide it. The page refreshes its status while an update is starting or active and stops as soon as the run completes with any result.
  • Active updates record a heartbeat about every 10 seconds. If no heartbeat is received for more than 90 seconds and the updater lock is no longer held, the run is marked failed automatically and page refreshing stops.
  • The page identifies the selected update type while an update is starting or running. Recent Update Runs shows server-local start and finish times, source, cycle, result, and message for each attempt, including successful conditional checks that required no staging rebuild.
  • Use Show Logs for a run to open Admin: Airport Update Logs with that attempt selected. Logs include download, staging, validation, warning, promotion timing, and failure diagnostics when available.
  • Promotion, backup restore, stage clearing, and backup deletion remain separate controls so downloading new data does not automatically replace production data.
  • Airport matching uses durable NASR and OurAirports source identities. Airport codes are used only as same-type fallback evidence because codes can change or be reassigned.
  • NASR and OurAirports records are combined only when their identifier match is supported by valid locations within 1 NM. Missing or materially different locations keep the records separate and generate an update warning.
  • If source identities and airport codes disagree, use Review Airport Identities before promotion. For each staged airport, choose Same Facility to preserve the selected production airport ID, or Different Facility to create a distinct airport. The page shows location, coordinates, saved-flight references, and active overrides to help with the decision.
  • Identity decisions apply only to the current ready snapshot and exact evidence. A new staging run invalidates stale decisions. Promotion remains disabled until every current conflict is resolved.
  • Promotion validates all identities before replacing the previous backup, so a rejected promotion does not discard the known-good backup.

Airport Identity Reconciliation

This NAS Data administration page appears when staged source identities cannot be mapped safely without a human decision.

  • Same Facility links the staged record to the selected production airport and preserves that production ID for saved flights and overrides.
  • Different Facility allocates a separate production airport ID. Use it when an airport code has been reassigned or the source record represents a genuinely different facility.
  • Same Facility, Different Facility, and Clear Decision queue choices locally without contacting the server. COMMIT saves every queued choice in one atomic request; CANCEL ALL discards all queued changes.
  • Leaving the reconciliation page with queued changes displays a warning because uncommitted choices will be discarded.
  • Review the staged and active-production cycle or validity periods, facility name, codes, the exact typed codes that matched, durable source IDs, location, distance between staged and production coordinates, saved-flight count, and active-override count before deciding.

Users

  • Create new users with an initial role and password.
  • Edit login name, display name, weight, role, and notes.
  • Set a new password for a selected user.
  • Lock or unlock a user account.
  • Deactivate or reactivate a user.
  • Saving individual permissions detaches that user from role-based permission inheritance.
  • Action-specific permissions are enforced independently of general Admin permission. Creating users requires Modify Person.
  • Changing person 0 or granting/removing Root Management requires person 0 or Root Management plus the acting user's current password.
  • Locking or deactivating an account immediately revokes its existing sessions. Reactivating it does not restore those sessions.

Roles

  • Create permission-template roles.
  • Edit role name, description, and permissions.
  • Role permission changes propagate to users still attached to the role.
  • Adding, changing, or deleting a role that grants Root Management requires Root Management and current-password confirmation.
  • Roles can be deleted only if they are not system roles and have no attached users.

Fuels

  • Create and modify fuel types.
  • Fuel types currently may be created and edited, but not deleted.
  • Check density and unit labels carefully, because they affect W&B calculations and display.

System Notices

  • Any user with Admin permission may create, edit, disable, or re-enable a system notice.
  • Notices are shown to signed-in users after the disclaimer. For an ordinary notice, DISMISS records that the user has completed the notice and prevents it from being shown to that user again.
  • A persistent notice can be dismissed for the current login, but is shown again at the next login. It continues to recur until its expiration date is reached or an administrator disables it.
  • RE-READ LATER continues the current login without dismissing the notice. The notice is shown again after the user signs in again unless it has expired or been disabled.
  • Non-root users can use Admin > System Notices to review and dismiss their active notices.
  • An optional expiration date expires the notice at the same Pacific-time time of day at which it was created.
  • Disabled notices are not shown to users. A disabled notice remains in the normal admin list until it expires, so an admin can edit or re-enable it.
  • The normal list excludes expired notices. Use SHOW ALL to include expired notices.

Failed Logins

  • Failed Logins is visible only to the root user. It shows failed sign-in attempts, including server-local date/time, client IP address, reverse-DNS status or hostname, Host header, Origin header, and user agent.
  • Attempts rejected after throttling or account lock are aggregated by IP and time window. The report shows the count, first and last attempt times, and details for the most recent 15 attempts in each aggregate.
  • The filter box accepts IP addresses, date/time values, the optional field names ip_address and datetime, the boolean operators AND, OR, and NOT, and parentheses for grouping.
  • Boolean shortcuts are also accepted: | for OR, & for AND, and ! or ^ for NOT.
  • A field name by itself means that the field has a value. For example, NOT ip_address finds rows where no IP address was captured.
  • Datetime values may be written as YYYY-MM-DD, YYYY-MM-DD HH, YYYY-MM-DD HH:MM, or YYYY-MM-DD HH:MM:SS. Quote date/time values with single or double quotes when that makes the expression clearer.
  • A bare date/time filter, such as datetime 2026-07-29, matches the whole supplied interval. With comparison operators, a date without a time means midnight at the start of that date, so BEFORE 2026-07-29 means before July 29, 2026 at 00:00:00.
  • Datetime operators include BEFORE, BETWEEN, and AFTER. Symbolic forms are <, ≤, - for between, ≥, and >.
  • Not-equal filters use != or ≠, for example ip_address != 10.30.97.6 or datetime != 2026-07-29.
  • BEFORE, BETWEEN, AFTER, <, ≤, ≥, and > may be written either after datetime or by themselves when the expression is clearly a datetime comparison.
  • Examples: 10.30.97.6 OR ≤2026-06-10, ip_address = 203.0.113.7, BEFORE "2026-07-29", datetime AFTER "2026-07-28 14:30", datetime BETWEEN "2026-07-01" AND "2026-07-28 23:59", datetime "2026-07-01" - "2026-07-31", and (ip_address = 203.0.113.7 | ip_address = 198.51.100.9) & !datetime BEFORE "2026-07-01".
  • If the expression has no datetime condition, the report automatically limits results to the past four weeks.
  • If client-hostname lookups are pending, use Run Address Resolution to restart background reverse-DNS resolution and wait briefly for refreshed results.
  • Use Export Visible to download the same rows currently shown on the page. Use Export All to download all rows matching the current filters and sort order. Export formats are CSV and Excel .xlsx.

Config

  • Edit existing config-row values and descriptions inline.
  • Create new config rows when new keyed settings are needed.
  • Key and type are fixed after creation.
  • Debug flags such as debugging, debug.wx, debug.network, debug.wb, debug.form, debug.form_profile, debug.type, and debug.hostname are controlled here.

Template Administration Notes

  • Templates follow owner/admin visibility and edit rules.
  • Delete on the Templates page means disable, not physical purge.
  • Disabled templates stay visible to owner/admin on the Templates page, but disappear from normal flight form generation choices.