What is an IATA city code?

What is the difference between a city code and an airport code?

A city code names a place; an airport code names a field. Both are three letters, and both appear in the same boxes on a booking site, which is exactly why they get confused. An airport code identifies one airport and one only. A city code identifies the metropolitan area around it, so a search built on a city code can return flights arriving at any of the airports that an airline sells as serving that city.

The codes come from the International Air Transport Association (IATA). Its public code search is described as an official source for codes assigned by IATA, looks up the three-letter code of an airport, and returns up to five results for a query. [1] The same site lists a City Code Directory next to the Ticketing Handbook, Reservations Handbook and Airport Handling Manual, and offers reference data for airline, airport and intermodal location codes in its Airline, Airport and Location Coding Databases. [1]

The practical consequence is that codes are looked up rather than recalled. A three-letter combination that sounds right is not evidence that it is right, and the place to settle a question about a code is the IATA directory rather than a booking screen or a forum post. [1]

How do city codes work in flight search, award charts and fare rules?

It is the level at which a product is sold that decides which kind of code you meet. A fare rule or an award chart line is often written for a city pair, so a single line covers every airport in that area: that is the whole reason city codes exist. When a search runs on a city code, the results themselves are individual flights, each carrying its own airport code, and the cheapest or earliest result may not use the airport you had in mind.

The two levels also behave differently. Award space is held flight by flight, so two airports in the same city can show very different results on the same day, and a seat that is unavailable from one field may be open from another. Fare rules work in the other direction: a fare filed for a city pair may let the airline route you through any airport it treats as serving that city, which is what makes a city-code fare flexible in principle and vague in practice.

The way to keep control is to search at the level that suits the decision and then read the detail. Search the city to see everything available, then check the airport code, terminal and arrival time on each result before you choose; or narrow the search to a single airport code from the start. The award search workflow sets that sequence out step by step, and award chart route tables explain how chart lines are drawn between points.

Why can a city-code booking put you at an airport you did not intend?

If you accept the first result for a city pair, the airport inside that itinerary is the airline's choice within the city, not yours. It may sit on the far side of the metropolis, be reached by a long and costly transfer, or belong to a different cluster of airports from the one you know from previous trips. The same risk appears mid-journey: an itinerary can arrive at one airport in a city and leave from another, and the link between them is a surface journey that you have to plan and time.

None of that makes city codes unsafe; it makes them a search tool that needs a second look. Before paying, confirm three things: the airport code on every leg, how long it takes to reach the city from that airport, and, where the itinerary changes airports, how much slack you need. On tight itineraries the connecting time question is covered in the entry on minimum connecting time, and a wider view of how airports are grouped is in airports.

What a city code does not promise

• Not a guarantee of an airport. A city code is a search and fare convenience. It tells you which city an airline is selling; it commits the airline to a specific airport only once an itinerary naming that airport is issued.
• Not a ground transfer. Moving between airports that share a city code is not the airline's responsibility unless its own terms say so. Treat a cross-airport connection as your own arrangement, with the time and the cost that follow from it.
• Not owned by any one airline. The codes sit in the IATA directory rather than in a single carrier's system, and IATA publishes a City Code Directory and coding databases covering airport and intermodal location codes. [1]
• Not a statement of airline rules. Individual airlines set their own routing, change and cancellation conditions, and their own rules on missed connections. Those conditions are not covered here; read the fare rules for the specific ticket you are buying.

Frequently asked questions

Is an IATA city code the same as an airport code?

No. An airport code identifies one specific airport, while a city code identifies the metropolitan area and can therefore cover several airports. [1] Both are three letters, which is why the distinction is easy to miss on a booking screen.

Can I pick which airport in a city I fly into?

You can normally narrow a search to a single airport code instead of the city code. Either way, the itinerary you are issued names the airport, so check that name and code before you pay rather than after.

Does a city code cover only airports?

The coding system is not limited to airports: IATA offers reference data for airline, airport and intermodal location codes. [1] For any given city, look the code up in the IATA directory rather than assuming which points it includes.

Related pages

Airports, award search workflow, award chart route tables, minimum connecting time, and the full frequent flyer glossary.

Sources

Sources checked on 18 October 2026. It describes the IATA coding system itself: no airline or hotel loyalty programme is covered here, and the award charts, fare rules and ground-transport commitments of individual carriers sit outside this entry.

1. IATA airline and airport code search, checked 18 October 2026