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, Mx Window (maintenance), NAS Data for users with reference-data permission, and root-only Failed Logins and Check Config.

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.
  • NASR cycle labels use yynn: two-digit year and sequential cycle number, not calendar month. Some years have 14 cycles. The verifier uses numbered FAA edition metadata or the FAA's complete annual calendar cross-checked against a numbered edition, so a NASR preview need not wait for its own d-TPP XML. Verified evidence is cached under the runtime root and retained in nasr_cycle.json. If dates can be verified but the number cannot, the system displays Cycle unconfirmed rather than guessing. Missing or conflicting validity dates still stop the update without replacing Stage or active data.
  • Conditional NASR checks compare effective dates, so two editions in one month remain distinct. Show Logs includes conditional_decision.json with discovered source dates and the reasons for rebuilding or doing nothing. To replace a preview stage created with an old, incorrect cycle label, select Full rebuild and Download preview/next-cycle data; a conditional no-change check does not repair existing labels. The correctly labeled active edition is left unchanged.
  • 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.
  • NAS jobs have a unique operation identity tied to their build run. Job/run heartbeats and completion are published together, so delayed workers cannot overwrite a newer job. Abandonment checks acquire the updater lock and recheck build liveness before marking a job failed. Actual lock loss stops the current phase; inspect the per-run lock.log, heartbeat.log, and parent launcher.log before retrying. Incomplete stages are not promoted automatically.
  • 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.
  • New reference-data update runs also create summary.log. Its contents appear in Update Reference Data below Source selection (or the update information for non-preview runs). This automatic, non-AI summary groups warning entries into readable categories, provides a few example identifiers, and reports reconciliation separately. Counts are diagnostic entries, not distinct airports. Full details remain in the warning and evidence logs. Failed runs label warning review as incomplete; no-change checks do not claim to have repeated it. Missing evidence or unavailable summaries are stated explicitly. Older runs are not retroactively summarized.
  • Reference staging uses temporary disk-backed storage in the run's runtime working directory to reduce Python memory use on shared hosting. Allow additional temporary disk space; staging still uses one transaction and preserves the previous stage if loading fails. No increase to hosting or PHP memory limits is required by this change. Peak process memory remains available in the staging diagnostics. Temporary files are normally removed automatically; do not manually remove working directories while an update is active.
  • If a source fetch receives HTTP 503 (Service Unavailable), the failed update can show a dedicated diagnostic panel. It includes the original Retry-After header, when supplied, its suggested retry time in UTC when interpretable, and bounded plain-text excerpts from a follow-up response and the source home page. Missing, invalid, conflicting, or elapsed retry guidance is identified. These are upstream messages, possibly from an intermediary, not an application diagnosis or a promise that maintenance ends at that time.
  • 503 diagnostics make at most two short, size-limited additional requests per source/run and do not follow redirects. They never execute site scripts, interpret natural-language maintenance schedules, change source selection, schedule a retry job, or weaken download failure handling. Configured curl retries and existing cache behavior remain unchanged. Use Show Logs to read the source-specific *_http_503.json evidence; a source that subsequently completed successfully is not blamed for another source's failure.
  • The Reference Data operation card shows explicit status text: failed operations use a red alert, completed operations use a green notice, and queued/running or unknown states use a warning. A prior successful stage can remain available after a new update fails; that does not make the failed update successful.
  • 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.
  • Source matching uses the actual NASR ICAO identifier, not a guessed country prefix on a FAA identifier. For example, FAA AOC does not by itself trigger comparisons with PAOC or SAOC. Genuine FAA/local-code disagreements and actual ICAO coordinate disagreements still produce warnings. After deploying a source-matching correction, run Full rebuild or Forced complete rebuild; an existing staged snapshot and a conditional no-change result are not repaired automatically.
  • NASR is authoritative for US airports, including US territories; OurAirports is authoritative for known non-US countries. Country metadata determines authority, never an ICAO prefix. Missing or invalid authoritative fields may use supplemental data with the actual field provider recorded. Missing country is flagged as undetermined.
  • Conflicting source information generates warnings identifying the authoritative source. ICAO claims withheld to preserve uniqueness remain in the source evidence; facilities are not combined merely to remove a code collision. The system retains durable source identities and does not weaken the 1 NM location safeguard.
  • Equivalent US/territory country representations are recorded without a country-conflict warning. Historical AN versus BQ/CW/SX is accepted only with the same explicit ICAO code and valid locations within 1 NM; it is not a blanket country substitution.
  • Show Logs includes full source values and rejected candidate evidence in airport_source_evidence.log, all production reconciliation candidates in airport_reconciliation_evidence.json, and independent runway ownership/coverage accounting in runway_verification.json and runway_source_evidence.log. These reports survive working-file cleanup. Source-field differences are not additional manual identity cases; use the reconciliation counts to determine what requires a decision.
  • Chart Supplement (DCS) operational data and TPAs are matched to typed FAA airport identifiers, with verified NASR/DCS-coverage ICAO fallback. Coverage includes Kiribati, so Cassidy International (PLCH) can receive its FAA Pacific Chart Supplement data through a unique exact ICAO match without changing OurAirports' authority for its canonical fields. A foreign airport sharing an IATA or local code does not receive the US airport's runway instructions, clearance-delivery phone, or TPAs. Both airport records remain. Ambiguous or conflicting DCS identity evidence is omitted and reported as an airport_identity warning in the logs; inspect those warnings before promotion.
  • The reviewed ZUA/PGZU (Guam CERAP) and ZHN/PHZH (Honolulu air traffic control facility) pairs are non-airport entries. Their source rows are kept during processing (normal working-file cleanup still applies), but their information is not attached to airports. Their exclusion appears as non_airport_entry information in reference_data_info.log, once in building and once in staging, rather than inflating airport warnings or reconciliation counts. Unknown or contradictory identifier pairs are not silently excluded.
  • After a DCS matching-code correction, run Full rebuild (or Forced complete rebuild) to create a corrected stage, then review identity decisions and promote normally. Retain Download preview/next-cycle data when rebuilding a preview stage. Existing staged data are not repaired automatically, and a conditional no-change check does not rebuild them. No separate database migration is needed for the October 22 or October 25 DCS matching corrections.
  • 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.
  • If COMMIT is rejected, the error is shown without reloading the page. All queued choices, production-airport selections, and notes are retained so you can correct one decision and retry without redoing the others. Network or unexpected-response failures also retain the queue; an unconfirmed response does not prove whether the server committed it.
  • Controls are temporarily disabled during COMMIT or a bulk-proposal request to prevent overlapping requests or edits. Only a confirmed successful commit clears the queue and loads refreshed results.
  • 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.
  • The page distinguishes possible historical duplicates/source consolidations from other identity disagreements or incomplete evidence. Identity candidates must have valid locations within 1 NM of each other and compatible nonblank typed codes and countries; US/territory country representations are compatible. Distant candidates matched only by LOCAL codes, without shared durable identities, are shown separately and do not turn a historical duplicate into an identity disagreement. They remain visible and available for individual review. Nearby, unknown-location, occupied-ID, and stronger code evidence still block a bulk proposal. Triage counts cover only the current page, including resolved rows.
  • Each production candidate shows which of its source IDs also occur on the staged record. Review these matches as well as the typed code matches before selecting the production ID to preserve.
  • Source-Identity Providers identifies which provider owns each row's durable identity. Field Authority Policy separately states which provider should supply authoritative values: NASR for US/territory airports, OurAirports for non-US airports. These are different concepts; a US production row carrying only an OurAirports identity still has NASR field authority. Legacy rows explicitly say that detailed field provenance is unavailable. Expand the evidence to inspect original source values when recorded.
  • Queue Historical Duplicate Proposals makes one read-only server request covering up to 500 unresolved cases across all pages. It proposes retaining the existing NASR-backed internal ID only for a unique NASR/OurAirports owner pair with matching explicit source and staged ICAOs, valid nearby source/owner locations, no saved-flight or active-override references, and an available production target. Existing saved decisions, including stale decisions, and already queued choices are not overwritten. Other cases remain for individual review.
  • Inspect Queued Decisions: All Pages before COMMIT. Each bulk proposal identifies its target ID, ICAO, source identities, maximum separation, and zero-reference finding. Clear any individual proposal, including off-page proposals, or CANCEL ALL. Selecting a different target for a visible proposal makes it a manual decision. Bulk queues obey the 500-decision and 256 KiB payload limits; the status message identifies omitted cases. Leaving or reloading still discards uncommitted work.
  • COMMIT recomputes bulk eligibility from current evidence, including snapshot, fingerprints, target assignments, saved flights, and active overrides. A newly ineligible proposal rejects the entire batch without losing the local queue. Keeping a NASR-backed ID does not select NASR field values for a non-US airport: staged field authority remains unchanged. No proposal approves promotion or moves saved references automatically.
  • Download logs distinguish missing canonical ICAO metadata (information) from competing claims or unresolved source evidence (warnings), and identify the policy authority. NASR's raw ICAO_ID is retained separately from the selected canonical code. Informational entries are retained in reference_data_info.log and do not inflate warning counts.

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.
  • The Failure Reason column identifies unknown users, password mismatches, maintenance denials, rate limiting, inactive accounts, account lockouts, or authentication errors. No login name, person ID, password, or password verifier is recorded in these audit entries. Ordinary login failures still show the same generic message to the person signing in; detailed reasons are visible only to root.
  • A maintenance denial includes its maintenance-window ID in the MW ID column and recent-attempt details, whether the submitted login is known or unknown. Passwords are not checked for maintenance-denied users. When throttling prevents credential checking outside maintenance, the reason is Rate limited rather than a guessed credential failure.
  • Attempts rejected after throttling, account lock, or maintenance denial are aggregated by IP, reason, maintenance-window ID, and time window. The report shows the count, first and last attempt times, and details for the most recent 15 attempts in each aggregate. Historical rows without a recorded reason show Unspecified; reasons are not inferred retroactively.
  • 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; both include the failure-reason code and maintenance-window ID.

Check Config

  • Only root (person 0) can open this page. Click Check Config to test the effective Web PHP configuration and access permissions on the host serving the request.
  • The report shows the PHP handler and version, loaded ini files, environment loader if any, effective process identity when available, extensions, process execution, memory/time/upload limits, error logging, session/cookie settings, and session/upload directory access.
  • Application runtime directories are checked with private write/read/delete probes. Missing runtime subdirectories may be created; no configuration files or database rows are changed. A bounded PHP CLI child process is launched as a process-execution test.
  • Passwords, environment contents, cookie values, and raw exception messages are not displayed. Results are not cached by the browser.
  • A declared PREFLIGHT_ENV_CONTEXT is reported as INFO. If it is absent or empty, hostname-based Dev/Prod inference is reported as WARNING, with the hostname used. Unrecognized names leave the context unknown. This inference is diagnostic only and does not select environment files or change permissions.
  • Run pgms/CheckConfig.sh separately for the shell/CLI checks. A PHP environment file is not required when Apache SetEnv supplies the website's settings. Creating that file alone does not cause Apache to load it.
  • On HostGator, adjust domain PHP settings in cPanel's MultiPHP INI Editor. This page does not edit .htaccess, impose hostname restrictions, or test all converter/Python dependencies. Re-run it after deployment on each host.

Maintenance Mode (Mx)

  • Root and users with the effective administrator permission can open Admin > Mx Window to schedule maintenance or start it immediately. Other permissions, including reference-data administration alone, do not grant this authority.
  • Enter a required public message (up to 2,000 characters), choose an immediate or future start, and specify either a positive duration in hours/minutes or an end date/time. Start and end dates use US/Pacific (America/Los_Angeles), explicitly labeled PST/PDT. The database stores UTC. Nonexistent or ambiguous daylight-saving transition times are rejected; choose an unambiguous time.
  • Overlapping windows are rejected; adjacent windows are permitted. Duration is elapsed time, including when a daylight-saving change occurs. The duration limit is 87,600 hours and 59 minutes.
  • Select additional active non-admin users with the user-list checkboxes (maximum 500). Their selection is stored with that window. Root and current administrators are always eligible, but passwords, account activation, lockouts, disclaimer, and other normal access requirements still apply. To change a saved window or its user selection, cancel/close it and create another.
  • The login page shows the current or next window's message, start, end, and duration, while retaining its login form. During an active window, non-exempt users and unknown login names receive System undergoing maintenance, login not allowed. regardless of password correctness. These policy denials do not increment account password-failure counts; IP/login rate limiting remains in effect.
  • On page requests within the 10 minutes before a window starts, non-exempt signed-in users see a warning to save their work. This is a soft warning: no polling, proactive interrupt, or automatic page refresh is used. A page left idle may not show the warning until the next request.
  • Once maintenance starts, non-exempt sessions are revoked on their next request, before protected page actions run. The browser is returned to login. Existing PHP-session flight/loading draft data are retained for the same user, but unsent form edits cannot be recovered. Signing in as a different person clears those retained drafts. After maintenance ends, sign in again; revoked tokens are not automatically restored.
  • This also applies if an entire window starts and ends while a user is idle, even if it was scheduled after their last request. Their next request signs them out and explains that an intervening maintenance window requires a fresh login for system consistency, quoting that window's message. Canceled windows do not trigger logout; early closure uses the actual closing time. A fresh login after the window has closed is not affected by that window. Root, current administrators, and users selected for the relevant window remain exempt.
  • While signed in during maintenance, the header below the Rhino Aviation legend shows hours/minutes remaining. The countdown runs locally using the server-provided remaining time. An early closure or cancellation in another browser becomes visible on the next page request; the timer does not poll or reload a page containing unsaved work.
  • Use Cancel Planned Maintenance for future windows or Close Maintenance Now for an active window. Windows end automatically at their end time without cron, a background worker, or a required administrator request. The page retains the most recent 100 windows, their allowed-user lists, and closure history.
  • Deployment requires sql/AddMaintenanceMode_2026-10-19.sql, compatible with MySQL 5.7 and safe to rerun. Existing system notices and the NAS update-progress banner remain independent of maintenance access restrictions.

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.
  • Numeric and boolean rows use compact Value fields; other types keep full-width values with Type, Description, and Save on a second line. The dec type is an alias for decimal. Smaller screens stack the fields.
  • Delete Config Row matches whole keys, ignoring case. Only % and * are wildcards, matching zero or more characters. For example, form% matches form.converter.font_dirs but not debug.form; conv and conv% do not match that converter key, while *conv* does. Other characters, including underscores, are literal. A blank search lists all keys.
  • Select individual matches or Select all matching keys, then Delete. Confirm with CONFIRMED, or Cancel to retain them. The dialog names up to five keys; for larger selections it shows the count. Up to 500 keys may be deleted together. Deletion is permanent and applies only to the selected keys, not new matches added later. If any selected key was removed or renamed, the entire deletion is rejected; search again. Missing settings may use application defaults or cause features to become unavailable, so delete deliberately.
  • sys.limit.reference_download_concurrency limits simultaneous reference-data source jobs; sys.limit.reference_dcs_workers limits DCS PDF extraction workers. Both are positive integers, defaulting to 1. A value of 1 is serial/single-worker, not a boolean switch; zero is invalid. Changes apply when a new source phase/job starts. Missing, invalid or unreadable settings use 1. The old concurrency environment variables no longer override these DB values. Effective limits are recorded in the run logs even when debugging is off.
  • 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.