Some players using Starlink experience connection and geolocation issues with OnAir.

Starlink does not always provide an IP address that matches your real location, which may cause problems with certain game features (AI flights not showing on the map, synchronization delays, in-game panel issues, etc.).

Possible causes

Starlink uses CGNAT and dynamic IP addresses, which means the IP location may not match your actual location.

Traffic may be routed through a ground station far from where you really are, creating inconsistencies.

This can cause communication errors between your machine and our servers.

Solutions tested by players

Try another connection (5G hotspot, wired network) → helps confirm whether the issue is specific to Starlink.

Use a VPN with a dedicated/static IP → many users have solved the issue this way.

Example: setting up a VPN (like PIA or similar) with a fixed IP, and enabling “Bypass mode” on the Starlink modem.

Make sure the ports required by OnAir are open (TCP 11000 and 11001).

Adjust router/firewall settings: Enable port forwarding/triggering on the ports used by OnAir.

Allow OnAir through Windows Firewall and/or antivirus firewalls.

Expected result

With these workarounds, AI flights should appear correctly on the operational map, and synchronization should work without errors.

Notes

If you see your plane overshoot the airport slightly before turning back and landing, that is normal: the AI follows real-world approach patterns depending on wind and runway.

We are gathering feedback from Starlink users and will update this FAQ as more reliable solutions become available.