Troubleshooting

This section provides solutions to common issues with FlightRadar.

Quick Diagnostic Checklist

Before drilling in, check the basics:

  • [ ] Is the LCD lit? (If not, check USB-C power and the cable)

  • [ ] Does the clock (top-right) show the correct local time? (If not, WiFi/NTP hasn't synced)

  • [ ] Is the device on your WiFi? (No traffic + wrong clock usually means it's offline)

  • [ ] Is your home location correct? (Settings → LOCATION)

  • [ ] Is the range sensible for your area? (the + / − buttons on the scope)

WiFi and Setup Issues

The WiFi Scan Shows No Networks

Possible causes and solutions:

  • 5 GHz only — FlightRadar supports only 2.4 GHz. Enable 2.4 GHz on your router.

  • Out of range — move the device closer to your access point.

  • Hidden SSID — hidden networks don't appear in the scan. Tap Other (enter manually) and type the name.

  • Scan still running — give it a few seconds, or tap Rescan.

Can't Connect to the WiFi Network

  • Wrong password — re-enter it; passwords are case-sensitive. Delete the network in Settings → WIFI and add it again.

  • 2.4 GHz disabled / band steering — ensure the 2.4 GHz band is enabled; some routers hide it behind a single combined SSID.

  • Special characters — very unusual characters in the SSID or password can cause problems; a simpler guest network is a good test.

Can't Reach the Setup Page (Access-Point Mode)

If you're using the phone/laptop fallback:

  • Make sure you joined the open network named FlightRadar Setup.

  • If the captive portal doesn't pop up, open a browser and go to http://192.168.4.1.

  • Temporarily disable mobile data / "auto-switch to mobile" so the phone stays on the setup hotspot (which has no internet).

No Aircraft on the Scope

Symptoms: WiFi is connected and the clock is correct, but the scope shows no blips.

Possible causes and solutions:

  1. No traffic in range right now

    • During quiet periods there may genuinely be nothing overhead.

    • Zoom out with the − button on the scope to a wider range (e.g. 80–250 km) to see distant traffic.

  2. Wrong home location

    • If the scope is centred on the wrong place, real traffic falls outside your range.

    • Check Settings → LOCATION and set your correct grid or coordinates.

  3. No internet access

    • The feed needs outbound HTTPS. If your network blocks it, no positions arrive.

    • Confirm the device is truly online (the clock will be correct after NTP) and that outbound HTTPS to opendata.adsb.fi is allowed. See Advanced Features.

  4. Feed service temporarily unavailable

    • The adsb.fi network is a community service and can occasionally be slow or down.

    • The device retries automatically; wait a few minutes.

Detail Panel Missing Type / Route

Symptoms: A selected aircraft shows altitude, speed and heading, but the type, operator or route stay as unknown aircraft / route unknown.

  • The core fields come from the position feed and are always present. The type/operator and route are looked up from adsbdb.com and depend on that database having the aircraft or the flight number.

  • General-aviation and military aircraft often aren't in the route database.

  • A brief looking up aircraft... / looking up route... is normal while the lookup runs; give it a few seconds.

  • If every aircraft is missing enrichment, the device may be unable to reach api.adsbdb.com — check outbound HTTPS (see Advanced Features).

Clock Is Wrong or Shows --:--:--

  • The clock is set by NTP after WiFi connects. A wrong or blank clock almost always means the device isn't online yet.

  • Fix the WiFi connection first; the clock corrects itself once NTP syncs.

  • Check the timezone in Settings → TIMEZONE if the time is offset by whole hours.

Display Issues

Screen Is Blank / Dark

  • Power — verify the USB-C cable is fully seated and the supply provides at least 1 A. Try a different cable/adapter (some cables are charge-only or too thin).

  • Night Mode — if the screen goes dark on a schedule, it's Night Mode. Touch the screen to wake it for a few minutes, or disable the schedule in Settings → NIGHT MODE.

  • Boot loop — an underpowered supply can cause repeated restarts. Use a known-good 1 A+ USB-C supply.

Everything Is Upside-Down

  • The screen rotation is set to 180°. Change it in Settings → SCREEN to NORMAL.

Touch Doesn't Line Up

  • Rotation flips the display and touch together, so taps should always align. If they don't, toggle Settings → SCREEN between NORMAL and 180° once to resync, or power- cycle the device.

Firmware Update Issues

  • Update won't start / "check failed" — confirm the device is online and can reach u.topbytes.net over HTTPS. Retry from Settings → SW UPDATE.

  • Update fails partway — the device shows Update failed. Resuming. and keeps the existing firmware. Check WiFi stability and try again; updates resume cleanly.

  • Beta prompt appears unexpectedly — a pre-release build was offered. Tap CANCEL to stay on your current firmware.

Getting Help

Gathering Information for Support

Before contacting support, note:

  • Device ID (MAC) — from Settings → ABOUT

  • Firmware version — from Settings → ABOUT

  • Your WiFi type (confirm it's 2.4 GHz) and whether the device shows as online

  • A clear description: what you did, what you expected, and what actually happened

Serial log output (115200 baud over USB-C) can also help — it shows the boot, WiFi, NTP and feed activity. Typing stat on the serial port prints a one-screen status summary (version, time, WiFi, home, aircraft in range and memory).

Contact Support

Emergency Recovery

If a firmware update fails badly or the device stops functioning, you can re-flash it directly from a computer.

You will need a USB-C cable that carries data (not charge-only). Plug FlightRadar into your computer.

Note

Use the Google Chrome web browser to perform the recovery flash.

Click the "Connect" button above and select the USB serial port associated with your FlightRadar, then follow the prompts.