The map’s aircraft, as JSON

Yes, for both the REST API (api.flyitalyadsb.com/v2/*) and the MCP server (flyitalyadsb.com/mcp) — same key for both, passed in the X-Api-Key header. It's self-service and instant: just an email address: within seconds you get a link to see the key, no manual approval. The key is free; paid plans raise its limits without changing it.

Tracks are an aircraft’s path point by point. For the Boeing 737 EI-EGD on 7 November 2026, /v2/history/4ca8af/2026-11-07 returns 4,597 positions, each with time, coordinates, altitude and speed. The flight history is what we build from those tracks every night: for the same aircraft and day, /v2/flights/reg/EI-EGD?from=2026-11-07&to=2026-11-07 returns 7 flights (Bergamo–Tirana, Tirana–Bergamo, Bergamo–Eindhoven and so on), with departure and arrival airport, times and duration. To know where an aircraft was and how high, use the tracks; to know where it took off and where it landed, use the flight history.

The flights our network saw, rebuilt every night from the tracks: departure and arrival airport, times and duration. You search it by aircraft (registration or ICAO address, with the flight log as CSV too), by callsign or flight number (where FR5518 flew in the last days and its usual routes), by airport (a day’s departures or arrivals) or by route. How far back depends on the plan: Free 7 days, Starter 14, Pro 30, Fleet 90; it starts on 23 October 2026. These are not airline schedules: no future flights, and if the network did not see a takeoff or a landing that end stays empty.

An aircraft’s path on one day, point by point: time, position, altitude, speed and heading. /v2/history/{icao} lists the days with a track, /v2/history/{icao}/{date} returns one day’s track, and ?since= returns only the new points of today’s. Use them to replay a flight on a map, find where an aircraft was at a given time, or match it against another recording. Full tracks exist every day since 17/08/2026; for older days, see “How far back do tracks go?”. How far back you can read them depends on the plan: Free the last 7 days, Starter 30, Pro 90, Fleet the whole archive since 2022.

On Fleet your account has a list of aircraft, up to 25: you add them with POST /v2/watch by ICAO address, registration or callsign, or from the chat with the watched_aircraft MCP tool. A webhook with kinds takeoff and landing receives flight.takeoff and flight.landing for each of them, with the airport and the time, wherever it flies. We detect them in real time from our receivers: a takeoff or a landing the network does not see is not sent. For more than 25 aircraft, write to [email protected].

The flight history stops at yesterday. On Fleet, /v2/flights/icao, /reg and /callsign add today: the day’s flights so far, from takeoffs and landings detected in real time, each with its status (landed, in flight or unknown). The aircraft does not need to be watched. For an aircraft in flight there is an estimated arrival when its callsign has a usual route leaving from today’s airport: it is the distance divided by the current speed, not a schedule, and while the aircraft climbs it comes out late. The next night the day goes into the flight history.

A monthly subscription paid by card or wallet, prices before tax: your country's tax is added at checkout. Change plan or cancel any time from the links in your receipt; a cancellation takes effect at the end of the period and the key goes back to the Free plan. The data stays CC BY-SA 4.0: a plan pays for access and higher limits, not for a different licence.

No plan includes an SLA or guaranteed response times, for the API or for email: FlyItalyADSB is a community and the paid plans only cover the cost of servers and bandwidth. The service is best effort and we reply as soon as we can. An SLA can only be agreed in a tailored agreement: get in touch.

By area first: each request asks for the aircraft in a circle, and the maximum radius depends on the plan: 500 km on Free, 1,000 km on Starter, the whole world in one request on Pro and Fleet. Then by volume, requests a minute and a month, counted on the key. When you choose a paid plan we tell you if, in the last 7 days, your email’s key asked for more than that plan allows.

Yes, on every plan, free included, within that plan's limits. Above the free limits you need a paid plan (Starter from €9/month, Pro, Fleet): self-serve, cancel any time, the key you already have is upgraded in place. You can use it inside apps and devices you sell too (see below). If you need more, that is reselling the data as an API or feed for other people's products, an SLA, more than 25 aircraft or more volume, get in touch and we'll agree something tailored.

Yes. The key can be built into an app or device you distribute or sell, and your server can use it, caching included, to serve your product's users. Requests from all the devices and users count together towards that key's plan: for example 10 devices asking 12 times a minute, day and night, make 120 requests a minute and over 5 million a month, which is the Pro plan. Use one key per product and credit FlyItalyADSB and flyitalyadsb.com in the product (CC BY-SA 4.0). A key inside an app can be extracted: to keep it safe, use it only from your server. To resell the data as an API or feed for other people's products, get in touch.

Almost all of it from the receivers of the FlyItalyADSB network, which send us their data first-hand, and from our own multilateration (MLAT). A small part comes from outside sources: ADSBHub and, for gliders and ultralights, the Open Glider Network (OGN). Aircraft seen only by those sources are about 1% of the total (measured on 19 October 2026): if one of them stops, the rest is unaffected.

The picture of every aircraft refreshes every half second, on the map and in the API. Each aircraft carries seen_pos, the seconds since its last position: in a measurement on 19 October 2026 half of the positions were under a second old and 9 in 10 under 7 seconds. Positions older than about 60 seconds are not returned.

Each aircraft is a record in readsb's aircraft.json format, the same as tar1090: ICAO hex, callsign (flight), registration (r) and type (t) for about 99% of aircraft, position, altitude, speed, track, squawk, category and the military, PIA and LADD flags. There is no route (departure and arrival airports) and no photos: for those you need another source.

Yes: /v2/lat/<lat>/lon/<lon>/dist/<km> returns every aircraft within the radius. The maximum radius depends on the plan: 500 km on Free, 1000 km on Starter, no limit on Pro and Fleet, which can ask for the whole world in one request. For several specific aircraft one request is enough: /v2/icao/a,b,c (or reg, callsign) looks up to 50 together and counts as one.

No, it is a global network: about 3,200 receivers around the world send their data directly to us, and the REST API and the MCP server answer for any point on the planet. Coverage is densest in North America and Europe: of the receivers that share a position, about 36% are in the United States, 15% in Germany, 11% in the UK and Ireland and another 16% in the rest of Europe (26 October 2026). Asia, Australia and New Zealand follow; Latin America and Africa are thinner. Italy is where the project started, in 2020, and where the name comes from. For a given area, check the live map or try a request with a Free key.

The full comparison is at flyitalyadsb.com/data/comparison: features, limits, feeder requirements and commercial-use terms for each, from their public documentation. In short: among those APIs, FlyItalyADSB is the only one that allows commercial use on the free tier; the Pro plan covers the whole world in one request; with the same key you get the FlyItalyADSB format (/v2), the ADS-B Exchange v2 format (/api/aircraft/v2: same paths, key headers and JSON, only the host and the key change), history, events by area and an MCP server for AI assistants.

Yes: an overflight is an aircraft that passed near a point. /v2/overflights?lat=&lon=&dist=&from=&to= lists the aircraft that passed within dist km of a point in that window, with the time and distance of the closest point, the lowest altitude and the source (ADS-B or MLAT). The current day reaches up to about 10 minutes ago, and the response always says which period it covers. From Starter up, per request: Starter 10 km and 6 hours, Pro and Fleet 50 km and 24 hours; since 17/08/2026. It is about aircraft, not people: we don’t know who was on board.

Yes: ask your assistant about an aircraft and it will use aircraft_profile, or call /v2/profile/{icao}: identity, whether we see it now and where, first and last day in the history. The photo isn’t in the answer, because Planespotters.net’s terms don’t allow it: you get the link to their page, with the photographer’s name, and the map link. No photo link for PIA and LADD aircraft. Never owner names.

Yes: whoever feeds FlyItalyADSB gets the Pro plan limits and features on their Free keys at no cost (300 requests a minute, 10 million a month, worldwide radius, overflights, emergencies, tracks of the last 90 days and the runway in use; area alerts stay with the paid plans), for non-commercial use. Turn it on in My API by opening the page from the same network as the receiver: we check that data arrives from there, as on the "Is my data arriving?" page. It lasts as long as the receiver feeds the network, with 3 days of grace if it stops.