How We Built Pages for 4,225 Cities With an Airport

Cities with airports list is really a question about how many places in our own dataset have at least one airport worth a page, and the answer is 4,225. Every one of those cities gets a page on TrackMyWings™, built the same mechanical way from the same 4,563 airport records, and most of the time that page quietly points a search engine back at a single airport instead of standing alone. Here is exactly how the pages are built, why most of them work that way, and where the underlying airport data comes from.

How a city gets its own page

Every airport in our dataset carries a city name and a country code. To turn those two fields into a web page, we lower-case the city name, collapse anything that is not a letter or a number into a hyphen, trim the stray hyphens off each end, and append the lower-cased country code. Munich, Germany becomes munich-de. New York, United States becomes new-york-us. That function is called once per airport record, and every distinct result it produces becomes a slug in our system. The same rule handles spaces, apostrophes and accented letters: anything that is not a plain letter or number becomes a hyphen, so every city name still produces one clean, lowercase slug.

At build time, we collect every distinct slug that comes out of that process and generate one static page for each. That is where 4,225 comes from: it is not a target we picked, it is simply how many distinct city-plus-country combinations exist across the 4,563 airport records in our dataset once the slug function has run over all of them. The country code in the slug is doing real work: without it, two unrelated cities that happen to share a name would collide into one page. Slugging by city name alone would merge them; slugging by city and country keeps them apart.

What's actually on a city page

A city page is deliberately narrow. It lists the airports that share that city's slug, each one linking through to that airport's own page, where the airport's name, IATA and ICAO codes, and location live. It is an index, and its entire job is pointing a visitor at the right airport page for the city they typed in. Each airport name on a city page links straight through, so a visitor who searched by city is one click from the airport they meant. For a traveller who knows the city but not the code, that is the whole point of the page.

That narrowness matters because it means the count of city pages is a fact about how many distinct cities appear in our airport data, nothing more. Whether an airport is a major international hub or a medium regional airport, if it carries a city and a country in the dataset, its city gets a page.

Why most city pages point back to a single airport

Of the 4,225 city pages, 4,062 have exactly one airport listed. A page for a city with only one airport is, in substance, the same content as that airport's own page rendered a second time, so rather than let two nearly identical pages compete against each other in search results, the single-airport city page sets its canonical tag to point at the airport's own page instead of asking to be indexed on its own. That is a standard way to avoid two pages splitting the same search relevance for the same query.

Practically, this means a visitor who lands on a single-airport city page and a visitor who lands on that same city's one airport page end up looking at pages built to be treated as the same destination by a search engine, even though both render and both work as links.

This is not a special case bolted on for city pages. Any two pages describing the same underlying thing in nearly the same words face the same choice: index both and let them compete, or point one at the other and let the stronger page carry the query. For 4,062 of our 4,225 cities, the airport page is the stronger, more specific one, so the city page defers to it. The 163 cities with more than one airport do not have that option, because no single airport page can stand in for a whole city's worth of airports, which is exactly why those pages are built to stand on their own instead.

The 163 cities with more than one airport

The remaining 163 city pages have two or more airports listed, and those are the pages where the city index genuinely earns its place, because a visitor searching by city name has a real choice to make. London, New York and Chicago are among them. On each of those pages, the point of the page is exactly what a single-airport page cannot offer: a real choice between named airports serving one city, each linked through to its own detail page.

Most city pages look like Munich or Stuttgart instead: one airport, listed and linked, with the city page deferring to that airport's own page.

Where the airport data comes from

Every record behind these pages comes from OurAirports, a public dataset of the world's airports. Our build process downloads that data and keeps only the airports that carry a three-letter IATA code and are classed as a large or medium airport, which is why the 4,225-city count reflects commercially relevant airports rather than every landing strip on Earth. Small grass strips, private airfields and airports without an assigned IATA code are filtered out before the city slugs are built. OurAirports releases its airport data to the public domain.

The counts in this post are as of 2026-09-23.

How TrackMyWings helps

TrackMyWings™ is a live flight-tracking platform in development, built for the person waiting on a flight as much as the person flying it. A private beta shipped on 2026-08-24, Android only, on the Play internal testing track. Public launch has no fixed date; it depends on trade-mark clearance and on the app being good enough to earn the download.

Questions people ask

How many cities with an airport does TrackMyWings list? 4,225, based on the distinct city-and-country combinations in our airport dataset as of 2026-09-23.

Why does my city's airport page redirect me to the airport itself? It does not redirect; the page still renders. But if that city has only one airport in our data, the page sets its canonical tag to the airport's own page, because the two pages would otherwise be near-identical and compete for the same search result.

Which cities have more than one airport in your data? 163 of the 4,225, including London, New York and Chicago. Each of those pages lists its airports, each linked to its own page.

Where does the underlying airport data come from? OurAirports, a public-domain dataset, filtered to airports with a three-letter IATA code and a large or medium airport classification.

Why does a city slug carry a country code? Because two unrelated cities can share a name. Adding the two-letter country code, as in munich-de, keeps each one on its own page.

Sources

• OurAirports, "Data," https://ourairports.com/data/, captured 2026-09-23