FLIGHTWATCH / FAQ
A few things to know.
Straight answers about control, communications, licensing and local features.
Does FlightWatch control my aircraft automatically?
No. FlightWatch is a companion application and does not control your aircraft automatically.
Does it auto-tune radios?
No. Tuning and swapping require explicit user action.
Does it predict which controller will come online?
No. It monitors the current live ATC route and available network information.
Does it require VATSIM?
Core live network features require VATSIM.
Does it require vPilot?
vPilot and FlightWatch.VPilotBridge.dll are required for vPilot communication integration. VATSIM data and ATC Route can still function without the bridge.
Does FlightWatch collect hardware IDs?
No hardware fingerprinting. It does not collect MAC addresses or disk / motherboard serial numbers.
Does uninstall remove the license identity?
Normal MSI uninstall preserves the local licensing identity, allowing it to be reused after reinstalling.
Does Mobile Receiver use the cloud?
No. It works over the local network without a cloud relay.
Can I use a POS printer?
Yes. Windows printers with configurable paper widths are supported.
Can the phone send commands?
No. The current Mobile Receiver is read-only.
Why is a controller in ALL but not in the timeline?
ALL is the online station catalogue. The timeline includes confirmed relevant stations from NOW towards the destination; passed or unrelated stations can remain searchable without being suggested as the next contact.
Does the runway diagram provide category C approach minima?
No. Geometry, elevation and runway wind are not published category-specific DA/MDA/RVR minima. Consult the applicable approach charts.
Is MSFS2024 compatibility confirmed?
Not across aircraft and integrations. MSFS2024 CHECK is a read-only diagnostic, not compatibility certification. Radio and aircraft telemetry require testing in your own simulator setup.