How FlyCodes builds its data
Every figure on this site is computed from two public datasets by a build script, not entered by hand and not estimated. This page states exactly what is computed, what it means, and what it does not mean.
Where the data comes from
Airports, runways and countries come from OurAirports, released into the public domain and actively maintained. Airlines and routes come from OpenFlights. Full licence details are on the data page. This copy was regenerated on .
How the connection ranking is computed
Every nonstop entry in the route file is reduced to an unordered airport pair. An airport's connection count is the number of those pairs that touch it; an airline's route count is the number of entries carrying its code. Airports are then ranked by that count, and that rank is what "#{n}by connections" means anywhere on this site.
What it is not: it is not a passenger total, not a movement count, and not an official statistic. A hub with many short thin routes outranks an airport with fewer, much larger ones. Where a page says "busiest", it means most connected in this dataset, and it is labelled that way.
Known limitations, stated plainly
- The route data is historical. OpenFlights routes have not been refreshed upstream in years. Carriers that merged or shut down are still listed. Route pages mark carriers that are no longer active, but the underlying connection may not exist today.
- Codeshares are included in the airline route totals. The source marks codeshare entries, and route pages exclude them so a carrier is never shown on a pair it does not operate. The per-airline route total on an airline page still counts every entry in the source file.
- Not every airport has a page. 5,333 of 8,803 airports have one. The rule is a usable IATA code plus either scheduled service or a large or medium field. The rest stay in search and in the API.
- Not every pair of airports gets a route page. Only the 6,000 most-flown pairs in the dataset do. Any other pair returns 404 rather than a page inventing a connection that has never been flown.
- Airline status is the source's flag. 983 of 1,105 carriers are flagged active. That flag ages with the file.
What is never done
No figure on this site is generated, estimated or inferred by a language model. If a field is missing from the source it renders as "not listed", never as a guess. Nothing on the site tracks you, and every lookup runs in your browser.
Who maintains this
FlyCodes is built and maintained by Dutch web agency FusionStudios. The dataset is regenerated when the upstream sources have changed materially, and the date of the current copy is shown on every page built from it.
Reporting an error
Send it through the contact form with the code and what you believe is wrong. Corrections that hold up against the sources are applied in the next regeneration; errors that come from the source data are reported upstream, because fixing them there fixes them for everyone.
Independence
FlyCodes is an independent project and is not affiliated with, endorsed by, or connected to IATA, ICAO, or any airline or airport. Do not use it for safety-critical or operational decisions; use the official publications for those.
Frequently asked questions
What does 'ranked by connections' mean?
It counts how many nonstop airport pairs in the open route dataset touch that airport. It is a measure of network centrality, not passenger numbers, and it is not an official traffic figure.
How current is the route and airline data?
The route file comes from OpenFlights, which has not been updated upstream in years. It is a historical snapshot: it still lists carriers that have since merged or closed. The copy on this site was regenerated on 2026-07-03.
Why do some airports have no page?
3,470 of the 8,803 airports in the dataset have no standalone page, because they have no scheduled service and are not a large or medium field. They stay searchable and stay in the JSON API.
How do I report an error?
Use the contact form. Corrections that hold up against the source datasets are applied in the next regeneration, and errors in the source are reported upstream to OurAirports or OpenFlights.
Data sources and licensing · About FlyCodes · The free JSON API