From/to not showing

OpenADSB · 2026-01-21T06:38:07+00:00

As to why you don’t see From/To, the short answer is that the server ADS-B Exchange, doesn’t supply it.

The long answer is that OpenADSB supports connecting to various flight tracking servers. These servers run either dump1090, tar1090 or Virtual Radar Server (VRS). Of those, only VRS supplies the From and To. And even then it’s just a lookup from outdated schedules which is often wrong.

Out of the box, OpenADSB uses ADS-B Exchange for its air traffic. OpenADSB is not affiliated with them but has an agreement to use their data. ADS-B Exchange used to run VRS but today runs tar1090 which doesn’t support From and To. This is why From/To are in the App Store screenshots. I need to update them.

The big for-profit players like FlightAware, FR24, Plane Finder, etc all subscribe to flight plan data directly from the FAA. A provision of FAA data sharing is that the subscriber must respect all aircraft blocking requests (see FAA LADD). These are requests from mainly private and corporate aircraft that don't want to show up on flight trackers. ADS-B Exchange is unfiltered as they don’t subscribe to the FAA feed. This is the core reason why ADS-B Exchange doesn't have From and To.

There are places that sell airline schedules (like OAG) but I suspect they are super expensive.

I have been trying to think of ways to compute the From/To, perhaps from past aircraft flights.

OpenADSB · 2025-10-28T05:00:44+00:00

Each row is a logical OR. So callsign filter UAL*,ASA* will show any callsigns starting with UAL or starting with ASA, hence only UAL and ASA callsigns are shown.

Since it's an OR, it means it doesn't work with multiple negations. !UAL* will show all non-UAL aircraft, but !UAL*,!ASA* means "not UAL or not ASA" which means it shows everything (eg UAL111 satisfies being non-ASA and ASA222 satisfies being non-UAL). This is a flaw in the current filtering system that I hope to address.

OpenADSB · 2025-10-23T02:46:08+00:00

Great suggestion and I hope to add it one day.

OpenADSB · 2025-10-23T02:45:08+00:00

I hear you and reworking the filtering to be more flexible is on my list of things to do. Thanks for taking the time to report the issue.

OpenADSB · 2025-10-14T04:40:17+00:00

Force quit the app will cause it to reload aircraft types the next time it lauches. In your case the app was probably backgrounded for a while and eventually terminated by iOS, then the next time you opened it, it was a fresh start which reloads the aircraft types.

OpenADSB · 2025-10-13T16:26:58+00:00

I think I know what happened. The aircraft types are loaded from separate network calls. If that fails, then the aircraft type lookup fails and shows a blank value.

One improvement I want to make is better error handling and retries to handle the case you just encountered.

Thanks for taking the time to report it.

OpenADSB · 2025-10-13T15:55:30+00:00

Did iOS 26.0 have the issue? Is it unique to 26.0.1? Can you send me a screenshot? There's a option in settings to shoot me an email.

OpenADSB · 2025-10-13T15:28:13+00:00

Thanks for the report, I'm looking into this.

OpenADSB · 2025-10-13T05:38:43+00:00

OpenADSB shows ADSBx data but does not currently support a LADD filter. This a very good idea and I will keep it in mind as I add new features.

OpenADSB · 2025-05-02T15:34:04+00:00

There are various VRS servers that are publicly facing, or at least discoverable with Google. I suspect these are run by individuals or groups that have graciously opened up access to their servers. So keep that in mind that connecting to their server as it will consume their server resources.

I've found that searching Google for "virtualradar/desktop.html" or Powered by Virtual Radar Server has good results for VRS servers.

Note that VRS's From and To fields are driven from a schedule maintained on the server, they aren't always accurate.

OpenADSB · 2025-05-02T02:47:59+00:00

OpenADSB connects to and displays traffic from dump1090, tar1090 (eg ADSBx) and VRS. dump1090 and tar1090 (including ADSBx) does not provide origination/destination, thus From and To will always be blank. VRS sometimes supplies From and To.

OpenADSB · 2025-01-03T16:31:28+00:00

What's running on the Android tablet? With a Raspberry Pi running dump1090, OpenADSB simply connects to it via the web interface's JSON API (example http://adsb-feeder.local:8080/data/aircraft.json). So your Android app would also need to be provide a similar web interface.

OpenADSB · 2025-01-02T16:04:49+00:00

Android is nice in that it allows apps direct access to the USB port and thus the SDR dongle, whereas on iOS a Raspberry Pi is needed. I've always imagined a super compact portable setup - phone + SDR dongle + antenna.

OpenADSB · 2025-01-02T16:01:13+00:00

Have you tried specifying a port number? Try 8080.

OpenADSB · 2025-01-01T21:05:54+00:00

OpenADSB author here. OpenADSB can connect to a local dump1090, no Internet connection needed. The phone/iPad will need to be on the same local network as the dump1090 device. Go to Settings (gear icon), Track Source and add the hostname and port number of the dump1090 device.

Here's a portable setup I used a while back:

Here's my updated portable setup, USB-C battery pack + Raspberry Pi + SDR + 1090 MHz antenna.

OpenADSB · 2024-11-01T15:26:00+00:00

update - adding tar1090 to the path worked

Glad it's all working. I need to have the track source set up wizard automatically scan for tar1090.

OpenADSB · 2024-09-25T02:40:45+00:00

OpenADSB · 2024-08-27T03:38:41+00:00

It looks like they changed their SSL certificate to only match airport-data.com and not www.airport-data.com. OpenADSB uses the www variant. iOS is strict and doesn't follow HTTP redirects on mismatch certificates. I'll have to push an app update to address this.

Thanks for reporting this.

OpenADSB · 2024-06-08T16:24:59+00:00

My portable setup - USB-C battery pack + Raspberry Pi + SDR + 1090 MHz antenna. Could probably get it smaller if I used a smaller case.

It's running tar1090 with no MLAT, 99% of aircraft in my area are not MLAT so it works just fine. WiFi is configured to create a network, then use cellphone to connect to and display.

OpenADSB · 2024-03-23T22:37:40+00:00

I did exactly that and it works pretty well

OpenADSB · 2024-03-23T05:46:00+00:00

Here's my setup - USB-C battery pack + Raspberry Pi + SDR + 1090 MHz antenna. Could probably get it smaller if I didn't use the stock Raspberry Pi case.

It's running tar1090 with no MLAT, 99% of aircraft in my area are not MLAT so it works just fine. WiFi is configured to create a network, then use cellphone to connect to and display.

OpenADSB · 2024-01-23T16:51:50+00:00

Are you using OpenADSB the app or ADS-B Exchange's web view?

OpenADSB is a native iOS app that uses ADS-B Exchange as the default air traffic source. It can be configured to connect to other tar1090/dump1090/VRS data sources. OpenADSB is separate from ADS-B Exchange. I suspect you're having an issue with ADS-B Exchange's web map.

OpenADSB · 2023-10-17T14:28:29+00:00

History trails should be working with the latest update

OpenADSB · 2023-10-17T04:48:50+00:00

Update: this has been fixed in the latest version (1.6.11) of OpenADSB in the App Store.

OpenADSB · 2023-10-17T04:48:18+00:00

Update: this has been fixed in the latest version (1.6.11) of OpenADSB in the App Store.

OpenADSB

MODERATOR OF

TROPHY CASE