Initial Admin Setup
Create the administrator password before exposing management controls.
The token is stored in C:\SkyTrace\SETUP-TOKEN.txt after the first start. It is destroyed when setup succeeds.
Create the administrator password before exposing management controls.
The token is stored in C:\SkyTrace\SETUP-TOKEN.txt after the first start. It is destroyed when setup succeeds.
Management controls are protected; the public flight display remains separate.
System health and the information you are most likely to need at a glance.
A concise operational summary. Detailed controls and diagnostics live in the sections at left.
Current application, canonical schema, and provider health.
Location, saved profiles, anchor airports, flight filters, and aircraft-data providers.
Set the geographic center and radius used for internet ADS-B queries and area tracking.
Exact coordinates and matched address details remain admin-only; the public display receives only the tracking label and radius.
Save airports, addresses, or custom coordinates as reusable tracking profiles. One tracking location is active at a time; these profiles are the foundation for later simultaneous multi-area and polygon tracking.
Save up to 6 airports of interest without moving the radar reference. SkyTrace identifies enriched flights as arrivals to or departures from these anchors; later builds will use the same anchors for airport boards and composable filters.
Composable filters for aircraft groups, cargo traffic, route geography, altitude, ground speed, airlines, and anchor-airport relationships.
All active filters are combined. An aircraft must satisfy every active rule to remain visible. Cargo classification uses operator/callsign metadata and a maintained cargo-carrier map. International/domestic filtering compares the enriched origin and destination countries; flights without enough route-country data cannot satisfy a geography filter.
All telemetry providers normalize into one SkyTrace schema. SkyTrace can fuse multiple enabled sources by ICAO address and preserve field-level provenance.
Build 20 separates your configured live-aircraft cadence from SkyTrace's protective effective cadence. Normal (5 seconds) is recommended for ADSB.lol. HTTP 429 responses automatically trigger exponential backoff, any Retry-After value is honored when available, and successful recovery steps gradually back toward your selected interval instead of immediately hammering the provider again. Cached last-good telemetry is retained through short throttling windows so a temporary rate limit does not instantly blank the radar. Local ADS-B polling remains independent. Fusion priority: higher values win when two sources have equally fresh telemetry. ADSBDB remains SkyTrace's primary aircraft/route enrichment provider; VRS standing data remains the secondary route fallback. The OpenSky adapter for the normal tracking-radius fusion pipeline remains separately gated. Build 47 keeps the Build 46 OpenSky global snapshot at zoom 3-5 and adds provider-friendly pacing to the ADSB.lol regional/detail engine at zoom 6+: no more than four regional radius requests are allowed in flight at once, a provider-wide cooldown is applied after HTTP 429 responses, Retry-After is honored when available, and cached traffic is retained while the provider recovers. Build 46 estimated-position continuity remains active for the global snapshot, and Build 44's atomic last-good generation protection still prevents a warming, failed, empty, or suspiciously small refresh from blanking the last complete map. The ADSB.lol bbox or official Flightradar24 bbox engines can still be selected explicitly with SKYTRACE_MAP_WIDE_PROVIDER.
Radar presentation and airport-weather settings.
Control the radar theme, flight trails, and the threshold used by the dedicated Overhead display.
Overhead predictions use current speed and ground track over a short horizon and are estimates, not ATC-grade trajectories. Radar theme changes the instrument surface only.
SkyTrace uses the Aviation Weather Center METAR feed for the reference airport weather strip.
Install updates, inspect rollback points, and create share-safe diagnostic bundles.
Install versioned SkyTrace ZIP updates with preflight validation, safety backup, restart, health check, and automatic rollback.
Every update creates a backup before touching the installed application. The newest backups are shown in a bounded scrollable list.
Support bundles remain safe to share for troubleshooting: they exclude database contents, admin security state, credential values, setup tokens, Cloudflare credentials, and precise tracking coordinates.
Complete backups and disaster-recovery controls. Detailed verification data stays collapsed until you need it.
Create and verify complete backups, preflight recovery media, and inspect recovery readiness when you need it.
Required checks cover the installed application, live SQLite integrity, settings/runtime, admin security state, Bootstrap Manager, the Build 24 recovery kit, a verified Complete Backup, Windows startup, and the configured public tunnel.
Creates a coherent, encrypted recovery source containing the SkyTrace application, SQLite state, settings, admin security state, bootstrap manager, release/update history, and portable machine-binding recipes. The passphrase is never stored by SkyTrace. Keep a downloaded copy somewhere other than this PC.
Verify a Complete Portable Backup before you ever rely on it for recovery. Preflight authenticates/decrypts the backup, checks every payload SHA-256, runs SQLite PRAGMA quick_check, checks required application/bootstrap files, compares machine bindings, and measures restore disk headroom. No installed SkyTrace files are changed.
1. On the replacement Windows PC, install 64-bit Python 3.11 or newer. Install cloudflared too if you want SkyTrace's existing public tunnel restored automatically.
2. Copy the Complete Backup ZIP and the Build 24 Recovery Kit to that PC. For a new Build 24 Format 2 backup, the hardened kit is already inside the backup ZIP under RESTORE-KIT.
3. Extract the Recovery Kit somewhere outside C:\SkyTrace, open PowerShell as Administrator, and run Restore-SkyTrace.ps1 -BackupPath "C:\path\to\backup.zip" -PreflightOnly.
4. If preflight passes, rerun the same command without -PreflightOnly. The kit re-verifies every staged file, rebuilds .venv, restores captured machine settings, creates and verifies a fresh SYSTEM startup task, attempts Cloudflare service recovery, starts SkyTrace, confirms the running Build matches the backup, writes post-restore verification records, and creates a portable recovery-report ZIP for troubleshooting.
5. Open the local Admin page, confirm your locations/anchors/filters/providers, verify the public hostname, then create a fresh Complete Backup from the replacement PC.