• OARC Flight Tracker - Map of flights being tracked by OARC feeders - there's also the feed checker, 12 hourly tracks at various altitudes, MLAT sync/map pages, system graphs and stats, and a live log of emergency flights tracked by the service
• Active trackers in OARC - Member list of people running flight trackers, with kit info and who they're feeding.

Update: 09/12/2023: You can now feed HFDL to the OARC tracker! Click here for more details.

Update: 11/02/2024: As a result of this HFDL feeding a little issue has cropped up. Some planes have the wrong hex code on HF vs ADS-B! Click here to read more about that and our solution to the problems it creates for the tracker.

OARC maintains a system for tracking the ADS-B data decoded by its members. They may already be feeding other sites, but this enables us to see just our members' data. We're doing this for the hell of it, to see what our combined coverage would be like, as well as learning how to administrate a system like this.

We've been able to build up a fairly robust network in a short space of time. This was inspired somewhat by the sale of ADSB Exchange to a private equity firm and our server is a completely unfiltered feed. If you're an OARC member and would like to contribute the information below should get you going.

If you have any specific questions ask in #adsb-flight-tracking on the OARC Discord.

For other useful information on setting up a system from scratch see this article detailing Mark 2M0IIG's journey into ADS-B reception. There's tips on hardware and software setup, antenna chat, and other information that may be helpful.

The server for the tracker was graciously donated by Mark 2W0YMS.

A full write-up of how this was done is being slowly developed here by Mark 2M0IIG and may be useful for those embarking on a similar ADS-B aggregator project.

If you already have a system (probably Linux-based) for receiving ADS-B data with the Beast data accessible on the standard port of 30005 and want to just install something to automatically feed OARC's system then please follow the instructions in the following repo: https://github.com/mpentler/oarc-adsb-scripts - these scripts are built off the adsbexchange system, so if you've installed that fine this will probably work for you also.

Otherwise you'll need a suitable SDR radio (probably an RTL-SDR or similar designed specifically for ADS-B reception) and a suitable Linux system for feeding. This is usually a Raspberry Pi, but it can also be run on normal Linux machines. We'll only cover RTL-SDR-based installs here as that is by far the most popular setup, but you may be able to use other radios with technology such as Soapy SDR or extra drivers.

Update 09/09/23: click here for some Windows instructions for decoding/feeding.

If you're already running a system built around one website (perhaps using a custom Raspberry Pi image) then there are scripts available to reconfigure your system to feed multiple websites. You could also manually configure things if you're confident. The key is to get your decoder app talking to your radio and offering up data on a network socket. Once that's done all other software can piggy back off that.

For an antenna you can make something really simple or buy something. A simple 1/4 wave ground plane built around a chassis connector for 1090 MHz connector works well, as does a collinear made from coax segments inside a PVC pipe. Feed the antenna with good coax with decent loss stats at this frequency. You can use cable TV 75 Ohm coax at a push and the loss stats are quite good @ 1090 MHz.

Once you've installed your OS you'll need to get the RTL-SDR stick going. On Raspbian this is sorted by default, but for other systems you may need to install the RTL-SDR drivers first.

After that you'll need to install the ADS-B decoder software that will use your RTL-SDR stick to decode the data and expose it to a network endpoint on localhost, ready for feeder software to pick up and send onwards to systems like OARC's.

Firstly install readsb for talking to your SDR and exposing the aircraft data on localhost:30005. Use the script here for that: https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb

This script will also install a local viewer, tar1090, at http://localhost/tar1090 so that you can see your traffic on a pretty map.

Do read the instructions carefully and make sure you understand how the software will interact with previously installed feeders, but things should be reconfigured at install time to make it all work. If you're using an image supplied by another tracker website or need a different custom setup and are unsure of how to proceed please ask in the Discord.

Update 02/10/23: here's a list of services/websites that you can feed. I will try and keep this somewhat up to date.

After you've done that you can start installing feeder software to send data to OARC and elsewhere.

If you already fed a website with a client that connected to the SDR on its own (as eluded to above), such as FlightRadar 24, you will need to check the config to make sure that it is reconfigured to read Beast data from localhost:30005 and not your SDR directly.

Use the script linked above in Prerequisites to feed OARC. Visit other websites to find out how to feed those. Generally there'll be a script to download and run. You'll need to provide your location and altitude to any sites that support MLAT if you'd like to send that data also.

There are detailed instructions for the OARC feeder and MLAT clients on the GitHub repo, and the process is quite automated and prompt-led. You shouldn't need TOO much support as long as your SDR works ok. Useful troubleshooting can be done by checking your system journal/log for messages relating to the loading of the drivers for SDR, as well as commands like lsusb to check connected device status.

Other components will log to the system journal/log and can help troubleshoot network or radio errors, as well as other system errors that may be stopping things working. Learning about basic systemd service control is useful here and will teach you some Linux skills at the same time. The services for the OARC feeds are oarc-adsb-feed and oarc-adsb-mlat and the master readsb service is just called readsb.

MLAT - multilateration - is the act of doing time-of-arrival analysis to triangulate the position of aircraft that aren't broadcasting full positional data. If an aircraft is only broadcasting Mode S data then there aren't any coordinates sent, so we have to do time-of-arrival analysis of the signal at multiple stations with known, accurate locations and compute a solution to where the aircraft probably is. This requires some clever maths relating to clocks and Kalman filters things like that.

The OARC tracker now supports MLAT and the feeder scripts have been updated to reflect this. Pick a username, add your coordinates and antenna height above sea level along with the unit (e.g. 81m) and let it all install. You'll see your dot on the Sync Map within a minute or two and the position will be somewhat hidden for your privacy. OARC MLAT results will be sent back to your local tar1090 view as well, as happens with other websites you may feed.

If you need to feed from Windows for some reason then here's some instructions. You'll need some different apps to the above but it should all work okay. Barry 2E0GTD has produced a visual guide here to help:

ToDo: add image